CVE-2026-73283

LOWPre-NVD 2.52.5—
EchelonGraph scoreHIGH 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 — 3 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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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(high)
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
0%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 11, 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 13× 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-08-20 03:33 UTCEG score recompute
  2. 2026-08-20 03:33 UTCGHSA enrichment
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-17 09:27 UTCEG score recompute
  5. 2026-08-17 09:27 UTCGHSA enrichment
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-14 15:23 UTCEG score recompute
  9. 2026-08-14 15:23 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-11 20:19 UTCEG score recompute
  12. 2026-08-11 19:30 UTCEG score recompute
  13. 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. 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.7% 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

Explore the affected products and dependency analysis for 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