CVSS 3.1
3.3 lowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NLow (3.3) in openbsd openssh. EPSS 0.08% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NExplain CVE-2026-106587 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106587?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106587?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106587 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| OpenBSD OpenSSH | before 10.6 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | openssh | no fix listed | DEBIAN-CVE-2026-106587 |
| Debian | 14 | openssh, openssh-gssapi | 1:10.6p1-1 | DEBIAN-CVE-2026-106587 |
| Ubuntu | 18.04:LTS, 20.04:LTS, 22.04:LTS and 3 more | openssh-ssh1 | no fix listed | UBUNTU-CVE-2026-106587 |
| Ubuntu | 22.04:LTS | openssh | 1:8.9p1-3ubuntu0.18 | UBUNTU-CVE-2026-106587 USN-8928-1 |
| Ubuntu | 24.04:LTS | openssh | 1:9.6p1-3ubuntu13.20 | UBUNTU-CVE-2026-106587 USN-8928-1 |
| Ubuntu | 26.04:LTS | openssh | 1:10.2p1-2ubuntu3.8 | UBUNTU-CVE-2026-106587 USN-8928-1 |
| Ubuntu | 26.10 | openssh, openssh-gssapi | 1:10.5p1-1ubuntu3.1 | UBUNTU-CVE-2026-106587 USN-8937-1 |
| Ubuntu | Pro:14.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS and 10 more | openssh | no fix listed | UBUNTU-CVE-2026-106587 |
| Red Hat | hummingbird:1 | openssh, openssh-keycat, openssh-server and 4 more | 0:10.5p1-1.2.hum1 | RHSA-2026:82247 |
| Azure Linux | 3 | openssh | no fix listed | AZL-106682 |
| Alpaquita | 23 | openssh | 9.1_p1-r16 | BELL-CVE-2026-106587 |
| Alpaquita | 25, stream | openssh | 10.6_p1-r0 | BELL-CVE-2026-106587 |
| BellSoft Hardened Containers | 23 | openssh | 9.1_p1-r16 | BELL-CVE-2026-106587 |
| BellSoft Hardened Containers | 25, stream | openssh | 10.6_p1-r0 | BELL-CVE-2026-106587 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpaquita · BellSoft Hardened Containers.
Red Hat rates this Low.
A low severity flaw was found in OpenSSH, affecting the openssh component shipped in Red Hat Hardened Images. Some sshd configuration options, including AuthorizedPrincipalsFile, are documented as accepting the value "none" to disable the corresponding feature. However, when such an option is overridden by a Match keyword in sshd_config(5), sshd incorrectly interprets "none" as a literal file path rather than disabling the feature. A local attacker with an unprivileged account on an affected system could exploit this by creating or manipulating a file named "none", potentially leading to improper access control enforcement or disruption of authentication or the sshd service. Exploitation requires a non-default configuration in which the affected options are set to "none" inside a conditional Match block. Red Hat rates this flaw as Low severity (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L), consistent with the upstream NIST rating of Low (3.3). A fix for the affected Red Hat Hardened Images stream is being pursued through the delegated resolution process.
As a workaround, avoid setting options that accept the value "none" (for example AuthorizedPrincipalsFile) inside sshd_config Match blocks, where sshd misinterprets the value as a literal file path. Instead, apply the "none" value at the global configuration level outside of Match blocks, where it correctly disables the feature, or restructure the configuration so that these options are not set to "none" via a Match keyword. This prevents sshd from reading a file named "none" that may be controlled by a local user. Alternatively, updating to a version of OpenSSH that includes the upstream fix resolves the issue.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | openssh-main-10.5p1-1.2.hum1 | Fixed 2026-10-13 | RHSA-2026:82247 |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-106587.