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 misread the setting “none” as a filename instead of recognizing it as a disabled option. This could allow an attacker to cause the server to read unexpected files, potentially leading to information exposure or service disruption. Upgrade OpenSSH to version 10.6 or later, or adjust the configuration to avoid using “none” where it could be misinterpreted.
What to do
- Update openeuler openssh to version 9.6p1-25.oe2403sp1.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| openEuler:24.03-LTS-SP1 | openeuler | openssh |
< 9.6p1-25.oe2403sp1 Fix: upgrade to 9.6p1-25.oe2403sp1
|
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-4692 · OSV
Track software like this
Free during beta