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.1%CVSS: 2.5Exploit: None knownExposed services: Not assessed

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.5LOWmedium confidence
EG Risk
16
EG Risk 16/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 11, 2026

Last Modified

September 4, 2026

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntussh-askpass-gnome (1:10.2p1-2ubuntu3.6) @ resolute2026-10-03ubuntu
redhatrhui5/rhua-rhel9:17902420042026-09-24redhat
redhatopenssh-main-10.5p1-1.hum12026-09-23redhat
redhatopenssh-0:9.9p1-11.el9_82026-09-21redhat
redhatopenssh-0:9.9p1-27.el10_22026-09-21redhat

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 rangeFix by version rangeDependents
openssh1:10.0p1-7 ... 1:10.4p1-5 (26 versions)
  • every version up to 1:10.5p1-1: fixed in 1:10.5p1-1
—
openssh-gssapi1:10.4p1-5
  • every version up to 1:10.5p1-1: fixed in 1:10.5p1-1
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssh—
  • every version up to 10.3_p1-r1: fixed in 10.3_p1-r1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssh1:10.0p1-1 ... 1:9.9p2-2 (77 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssh1:10.0p1-7 ... 1:10.5p1-1 (31 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 45× 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-10-03 20:27 UTCEG score recompute
  2. 2026-10-03 20:27 UTCVendor advisory
  3. 2026-10-03 20:27 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-01 19:50 UTCEPSS rescore
  6. 2026-09-30 22:01 UTCEG score recompute
  7. 2026-09-30 22:01 UTCVendor advisory
  8. 2026-09-30 22:01 UTCGHSA enrichment
  9. 2026-09-28 13:52 UTCEPSS rescore
  10. 2026-09-27 13:48 UTCEPSS rescore
  11. 2026-09-27 10:00 UTCEG score recompute
  12. 2026-09-27 10:00 UTCVendor advisory
  13. 2026-09-27 10:00 UTCGHSA enrichment
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-24 08:23 UTCEG score recompute
  16. 2026-09-24 08:23 UTCVendor advisory
  17. 2026-09-24 08:23 UTCGHSA enrichment
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-21 14:18 UTCEG score recompute
  20. 2026-09-21 14:18 UTCVendor advisory
  21. 2026-09-21 14:18 UTCGHSA enrichment
  22. 2026-09-20 20:16 UTCEPSS rescore
  23. 2026-09-18 19:36 UTCEG score recompute
  24. 2026-09-18 19:36 UTCVendor advisory
  25. 2026-09-18 19:36 UTCGHSA enrichment
Show 53 more
  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-16 14:08 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-16 01:31 UTCEG score recompute
  5. 2026-09-16 01:31 UTCVendor advisory
  6. 2026-09-16 01:31 UTCGHSA enrichment
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-13 06:39 UTCEG score recompute
  9. 2026-09-13 06:39 UTCVendor advisory
  10. 2026-09-13 06:39 UTCGHSA enrichment
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-10 12:34 UTCEG score recompute
  13. 2026-09-10 12:34 UTCVendor advisory
  14. 2026-09-10 12:34 UTCGHSA enrichment
  15. 2026-09-10 09:35 UTCEPSS rescore
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-07 16:47 UTCEG score recompute
  18. 2026-09-07 16:47 UTCVendor advisory
  19. 2026-09-07 16:47 UTCGHSA enrichment
  20. 2026-09-06 13:48 UTCEPSS rescore
  21. 2026-09-04 16:03 UTCEG score recompute
  22. 2026-09-04 16:02 UTCGHSA enrichment
  23. 2026-09-04 05:07 UTCEPSS rescore
  24. 2026-09-03 16:26 UTCEG score recompute
  25. 2026-09-03 16:26 UTCGHSA enrichment
  26. 2026-09-01 13:54 UTCEPSS rescore
  27. 2026-08-31 19:34 UTCGHSA enrichment
  28. 2026-08-31 04:25 UTCEG score recompute
  29. 2026-08-31 04:25 UTCGHSA enrichment
  30. 2026-08-28 21:42 UTCEPSS rescore
  31. 2026-08-28 10:20 UTCEG score recompute
  32. 2026-08-28 10:19 UTCGHSA enrichment
  33. 2026-08-26 14:47 UTCEPSS rescore
  34. 2026-08-25 15:43 UTCEG score recompute
  35. 2026-08-25 15:43 UTCGHSA enrichment
  36. 2026-08-25 13:49 UTCEPSS rescore
  37. 2026-08-23 00:19 UTCEPSS rescore
  38. 2026-08-22 21:38 UTCEG score recompute
  39. 2026-08-22 21:38 UTCGHSA enrichment
  40. 2026-08-20 22:56 UTCEPSS rescore
  41. 2026-08-20 03:33 UTCEG score recompute
  42. 2026-08-20 03:33 UTCGHSA enrichment
  43. 2026-08-17 13:47 UTCEPSS rescore
  44. 2026-08-17 09:27 UTCEG score recompute
  45. 2026-08-17 09:27 UTCGHSA enrichment
  46. 2026-08-16 14:56 UTCEPSS rescore
  47. 2026-08-16 14:56 UTCEPSS rescore
  48. 2026-08-14 15:23 UTCEG score recompute
  49. 2026-08-14 15:23 UTCGHSA enrichment
  50. 2026-08-12 13:51 UTCEPSS rescore
  51. 2026-08-11 20:19 UTCEG score recompute
  52. 2026-08-11 19:30 UTCEG score recompute
  53. 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 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.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73283?
CVE-2026-73283 has a CVSS base score of 2.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73283?
A fix for CVE-2026-73283 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73283 are linked in the Vendor Advisories panel on this page.

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.