cve.bz

CVE-2026-106588 openbsd openssh

3.1 lowEPSS 0.1%

Low (3.1) in openbsd openssh. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
In sshd in OpenSSH through 10.6, use of the macOS 27 (or later) SDK has the side effect of loss of sandboxing, which is potentially unexpected.

Severity

CVSS 3.1

3.1 low
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-653 Improper Isolation or Compartmentalization
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-106588 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106588?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106588?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-106588 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenBSD OpenSSHthrough 10.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 3 moreopenssh-ssh1no fix listedUBUNTU-CVE-2026-106588
Azure Linux3opensshno fix listedAZL-110501

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A flaw of low security impact was found in OpenSSH in the Red Hat Hardened Images (Hummingbird) context. When OpenSSH's sshd daemon is built using the macOS 27 (or later) SDK, the removal of the underlying macOS system interfaces causes the daemon to be built without its process sandbox. An sshd compiled in this way runs without sandbox isolation, so an attacker who compromises the daemon process could access system resources that the sandbox would normally restrict; this weakens defense in depth rather than directly exposing data or causing denial of service. Red Hat rates this flaw as low impact (CVSS 3.1 score 3.1, CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N), matching the upstream assessment. The loss of sandboxing only arises in builds compiled against macOS SDKs: Red Hat Hardened Images ships OpenSSH built as RPMs for Linux rather than against macOS SDKs, so the vulnerable build configuration is not present, and the Hummingbird affect is delegated with a not-affected resolution on that basis.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Hardened ImagesopensshNot affected

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-106588.

References

Check your stackJSON