Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.3
OpenSSH before 10.6 may treat "none" as a file
published 18 days ago
Summary
The OpenSSH server (versions earlier than 10.6) can misinterpret the setting "none" as a filename instead of recognizing it as a disabled option. This mistake could let an attacker influence how the system reads configuration or files. Upgrade OpenSSH to version 10.6 or later to correct the behavior.
What to do
- Update openeuler openssh to version 9.6p1-25.oe2403sp3.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| openEuler:24.03-LTS-SP3 | openeuler | openssh |
< 9.6p1-25.oe2403sp3 Fix: upgrade to 9.6p1-25.oe2403sp3
|
Original advisory text
openssh security update
An open source implementation of SSH protocol version 2
Security Fix(es):
In sshd in OpenSSH before 10.6, the value "none" for a configuration option is sometimes interpreted as a filename but was intended to mean that a feature is disabled.(CVE-2026-106587)
Security Fix(es):
In sshd in OpenSSH before 10.6, the value "none" for a configuration option is sometimes interpreted as a filename but was intended to mean that a feature is disabled.(CVE-2026-106587)
References
- https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-106587 Vendor Advisory
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit (estimated)
- Gives an attacker partial control (estimated)
Timeline
Published4 Nov 2026
Updated4 Nov 2026
First seen4 Nov 2026
Sources
OESA-2026-4690 · OSV
Track software like this
Free during beta