CVSS 3.1
4.3 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NMedium (4.3) in openbsd openssh. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NExplain CVE-2026-106586 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106586?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106586?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-106586 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-106586 |
| Debian | 14 | openssh, openssh-gssapi | 1:10.6p1-1 | DEBIAN-CVE-2026-106586 |
| Ubuntu | 18.04:LTS, 20.04:LTS, 22.04:LTS and 3 more | openssh-ssh1 | no fix listed | UBUNTU-CVE-2026-106586 |
| Ubuntu | 22.04:LTS | openssh | 1:8.9p1-3ubuntu0.18 | UBUNTU-CVE-2026-106586 USN-8928-1 |
| Ubuntu | 24.04:LTS | openssh | 1:9.6p1-3ubuntu13.20 | UBUNTU-CVE-2026-106586 USN-8928-1 |
| Ubuntu | 26.04:LTS | openssh | 1:10.2p1-2ubuntu3.8 | UBUNTU-CVE-2026-106586 USN-8928-1 |
| Ubuntu | 26.10 | openssh, openssh-gssapi | 1:10.5p1-1ubuntu3.1 | UBUNTU-CVE-2026-106586 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-106586 |
| 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-106688 |
| Alpaquita | 23 | openssh | 9.1_p1-r16 | BELL-CVE-2026-106586 |
| Alpaquita | 25, stream | openssh | 10.6_p1-r0 | BELL-CVE-2026-106586 |
| BellSoft Hardened Containers | 23 | openssh | 9.1_p1-r16 | BELL-CVE-2026-106586 |
| BellSoft Hardened Containers | 25, stream | openssh | 10.6_p1-r0 | BELL-CVE-2026-106586 |
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 security restriction bypass affects the openssh component in Red Hat Hardened Images (hummingbird-1). In OpenSSH sshd, the authorized_keys "restrict" keyword is intended to disable all forwarding features for a key, but it was not being applied to tunnel forwarding. On servers where tunnel forwarding has been enabled (the PermitTunnel option is disabled by default), an authenticated user connecting with a key restricted via "restrict" could bypass the intended access limitation and establish unauthorized network tunnels through the server. The impact is limited to integrity; the flaw does not directly affect confidentiality or availability. Red Hat Hardened Images is affected, and a fix is being pursued through the delegated hummingbird-1 update stream. Red Hat rates this flaw low severity (CVSS 3.1 score 2.5) because exploitation requires an authenticated user with an assigned restricted key and a non-default server configuration that enables tunnel forwarding; NIST has rated it moderate (CVSS 3.1 score 4.3).
This flaw only affects servers where tunnel forwarding has been explicitly enabled; PermitTunnel is disabled by default in OpenSSH sshd. As a workaround, tunnel forwarding can be disabled by setting "PermitTunnel no" in /etc/ssh/sshd_config (or removing any configuration that enables it) and restarting the sshd service, which prevents restricted keys from establishing network tunnels. This flaw can also be resolved by updating to the corrected openssh packages available through the affected Red Hat Hardened Images update stream.
| 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-106586.