In sshd in OpenSSH before 10.4, DisableForwarding=yes was supposed to take precedence over PermitTunnel=yes, but did not.
CVE-2026-59999
Score 5.9 from GitHub Security Advisory published 2026-07-08. NVD baseline CVSS 7.5; sources differ by 1.6.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 5.9(medium)
- EPSS
- 3.2%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 9, 2026
Advisory Details (3)
Auto-updated Jul 8, 2026oss-security - Announce: OpenSSH 10.4 released
https://www.openwall.com/lists/oss-security/2026/07/06/5'Announce: OpenSSH 10.4 released' - MARC
https://marc.info/?l=openssh-unix-dev&m=178333966933090&w=2Vendor Advisories for CVE-2026-59999(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-59999Microsoft Security Response Center (MSRC)Medium
In sshd in OpenSSH before 10.4, DisableForwarding=yes was supposed to take precedence over PermitTunnel=yes, but did not.
- GHSA-gcm2-x6hm-q4h3GitHub Security AdvisoriesMedium
In sshd in OpenSSH before 10.4, DisableForwarding=yes was supposed to take precedence over...
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | openssh-main-10.4p1-1.hum1 | 2026-07-09 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 00:43 UTCEG score recompute
- 2026-07-11 00:43 UTCVendor advisory
- 2026-07-11 00:43 UTCGHSA enrichment
- 2026-07-10 00:48 UTCEG score recompute
- 2026-07-10 00:48 UTCVendor advisory
- 2026-07-10 00:48 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 17:00 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
- 2026-07-09 00:51 UTCEG score recompute
- 2026-07-09 00:51 UTCGHSA enrichment
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 00:55 UTCEG score recompute
- 2026-07-08 00:55 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-59999?
When was CVE-2026-59999 disclosed?
Is CVE-2026-59999 actively exploited?
What is the CVSS score of CVE-2026-59999?
How do I remediate CVE-2026-59999?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59999
Is Your Infrastructure Affected by CVE-2026-59999?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.