Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.3
OpenSSH may treat "none" setting as a file
published 18 days ago
Summary
Versions of OpenSSH older than 10.6 on openEuler could mistake the word “none” in a configuration file for a file name instead of recognizing it as a disabled feature. This misinterpretation could let an attacker influence the program’s behavior. Upgrade OpenSSH to the latest release to correct the handling of the “none” value.
What to do
- Update openeuler openssh to version 8.8p1-52.oe2203sp4.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| openEuler:22.03-LTS-SP4 | openeuler | openssh |
< 8.8p1-52.oe2203sp4 Fix: upgrade to 8.8p1-52.oe2203sp4
|
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-4691 · OSV
Track software like this
Free during beta