CVE-2026-73283

LOWPre-NVD 2.52.5—
EchelonGraph scoreMEDIUM confidence

Score 2.5 from GitHub Security Advisory (severity: LOW) published 2026-08-11. a secondary CVSS source baseline 2.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
2.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.5Exploit: None knownExposed: 0

A fix is available — apply it.

In sshd in OpenSSH before 10.5, the restrict keyword (in authorized_keys) was supposed to be applicable to tunnel forwarding but was not.

CVSS v3
2.5
EG Score
2.5(medium)
EG Risk
16(Track)
EG Risk 16/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity25% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

August 11, 2026

Last Modified

September 4, 2026

References (1)

Vendor Advisories for CVE-2026-73283(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntussh-askpass-gnome (1:10.2p1-2ubuntu3.6) @ resolute2026-09-18ubuntu

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.

Affected Packages

(5 across 4 ecosystems)
Debian:14(2)
PackageVulnerable rangeFixed inDependents
openssh1:10.0p1-7 ... 1:10.5p1-1 (27 versions)——
openssh-gssapi1:10.4p1-5, 1:10.5p1-1——
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssh—10.3_p1-r1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssh1:10.0p1-1 ... 1:9.9p2-2 (77 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssh1:10.0p1-7 ... 1:10.5p1-1 (31 versions)——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

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 13× in last 7d / 43× 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.

  1. 2026-09-18 19:36 UTCEG score recompute
  2. 2026-09-18 19:36 UTCVendor advisory
  3. 2026-09-18 19:36 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-16 01:31 UTCEG score recompute
  8. 2026-09-16 01:31 UTCVendor advisory
  9. 2026-09-16 01:31 UTCGHSA enrichment
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-13 06:39 UTCEG score recompute
  12. 2026-09-13 06:39 UTCVendor advisory
  13. 2026-09-13 06:39 UTCGHSA enrichment
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-10 12:34 UTCEG score recompute
  16. 2026-09-10 12:34 UTCVendor advisory
  17. 2026-09-10 12:34 UTCGHSA enrichment
  18. 2026-09-10 09:35 UTCEPSS rescore
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 16:47 UTCEG score recompute
  21. 2026-09-07 16:47 UTCVendor advisory
  22. 2026-09-07 16:47 UTCGHSA enrichment
  23. 2026-09-06 13:48 UTCEPSS rescore
  24. 2026-09-04 16:03 UTCEG score recompute
  25. 2026-09-04 16:02 UTCGHSA enrichment
Show 31 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-03 16:26 UTCEG score recompute
  3. 2026-09-03 16:26 UTCGHSA enrichment
  4. 2026-09-01 13:54 UTCEPSS rescore
  5. 2026-08-31 19:34 UTCGHSA enrichment
  6. 2026-08-31 04:25 UTCEG score recompute
  7. 2026-08-31 04:25 UTCGHSA enrichment
  8. 2026-08-28 21:42 UTCEPSS rescore
  9. 2026-08-28 10:20 UTCEG score recompute
  10. 2026-08-28 10:19 UTCGHSA enrichment
  11. 2026-08-26 14:47 UTCEPSS rescore
  12. 2026-08-25 15:43 UTCEG score recompute
  13. 2026-08-25 15:43 UTCGHSA enrichment
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-22 21:38 UTCEG score recompute
  17. 2026-08-22 21:38 UTCGHSA enrichment
  18. 2026-08-20 22:56 UTCEPSS rescore
  19. 2026-08-20 03:33 UTCEG score recompute
  20. 2026-08-20 03:33 UTCGHSA enrichment
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-17 09:27 UTCEG score recompute
  23. 2026-08-17 09:27 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
  26. 2026-08-14 15:23 UTCEG score recompute
  27. 2026-08-14 15:23 UTCGHSA enrichment
  28. 2026-08-12 13:51 UTCEPSS rescore
  29. 2026-08-11 20:19 UTCEG score recompute
  30. 2026-08-11 19:30 UTCEG score recompute
  31. 2026-08-11 19:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73283?
CVE-2026-73283 is a low vulnerability published on August 11, 2026. In sshd in OpenSSH before 10.5, the restrict keyword (in authorized_keys) was supposed to be applicable to tunnel forwarding but was not.
When was CVE-2026-73283 disclosed?
CVE-2026-73283 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73283 actively exploited?
CVE-2026-73283 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.4% of all scored CVEs.
What is the CVSS score of CVE-2026-73283?
CVE-2026-73283 has a CVSS v3 base score of 2.5 (NVD).
How do I remediate CVE-2026-73283?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73283, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73283

Explore →

Is Your Infrastructure Affected by CVE-2026-73283?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs