CVE-2026-72924

LOWPre-NVD 2.12.1—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (15th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 2.1Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

GitHub CLI (gh) is GitHub's official command line tool. Versions 2.28.0 through 2.97.0 bind the local listener created by gh codespace ports forward to all available network interfaces by default. While port forwarding is active, a service in a Codespace can therefore become reachable through the user's non-loopback local IP addresses by other hosts that can route to the user's machine. This behavior does not change the GitHub-side visibility of the Codespaces port. Instead, it exposes the forwarded service through a wildcard-bound listener on the user's local machine, even when the source Codespaces port remains private. Exploitation requires a network-adjacent attacker to reach the victim's machine while forwarding is active. This issue is fixed in version 2.98.0.

CVSS v3
2.1
EG Score
2.1LOWmedium confidence
EG Risk
10
EG Risk 10/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
Severity21% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
15th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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 25, 2026

Last Modified

September 9, 2026

References (2)

Vendor Advisories for CVE-2026-72924(1)

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

Affected Packages

(2 across 2 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
gh2.23.0+dfsg1-1 ... 2.46.0-4 (16 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
gh2.46.0-3, 2.46.0-4
  • every version on: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 38× 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-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 21:16 UTCEG score recompute
  5. 2026-10-06 21:16 UTCVendor advisory
  6. 2026-10-06 15:18 UTCEPSS rescore
  7. 2026-10-05 17:43 UTCEPSS rescore
  8. 2026-10-04 23:22 UTCEPSS rescore
  9. 2026-10-03 16:17 UTCEG score recompute
  10. 2026-10-03 16:17 UTCVendor advisory
  11. 2026-10-03 14:26 UTCEPSS rescore
  12. 2026-10-01 19:50 UTCEPSS rescore
  13. 2026-09-30 06:22 UTCEG score recompute
  14. 2026-09-30 06:22 UTCVendor advisory
  15. 2026-09-29 15:24 UTCEPSS rescore
  16. 2026-09-28 13:52 UTCEPSS rescore
  17. 2026-09-27 13:48 UTCEPSS rescore
  18. 2026-09-26 21:37 UTCEG score recompute
  19. 2026-09-26 21:37 UTCVendor advisory
  20. 2026-09-26 15:59 UTCEPSS rescore
  21. 2026-09-23 17:54 UTCEPSS rescore
  22. 2026-09-22 18:52 UTCEG score recompute
  23. 2026-09-22 18:52 UTCVendor advisory
  24. 2026-09-21 21:09 UTCEPSS rescore
  25. 2026-09-20 20:16 UTCEPSS rescore
Show 38 more
  1. 2026-09-19 12:11 UTCEG score recompute
  2. 2026-09-19 12:11 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 07:11 UTCEG score recompute
  6. 2026-09-16 07:11 UTCVendor advisory
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-13 02:12 UTCEG score recompute
  10. 2026-09-13 02:12 UTCVendor advisory
  11. 2026-09-12 15:02 UTCEPSS rescore
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-10 09:35 UTCEPSS rescore
  14. 2026-09-09 21:13 UTCEG score recompute
  15. 2026-09-09 21:13 UTCVendor advisory
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-08 11:46 UTCEG score recompute
  18. 2026-09-08 11:46 UTCVendor advisory
  19. 2026-09-06 13:48 UTCEPSS rescore
  20. 2026-09-05 06:44 UTCEG score recompute
  21. 2026-09-04 05:07 UTCEPSS rescore
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-02 01:43 UTCEG score recompute
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
  26. 2026-09-01 04:40 UTCEPSS rescore
  27. 2026-08-30 19:18 UTCEPSS rescore
  28. 2026-08-30 19:17 UTCEPSS rescore
  29. 2026-08-30 01:22 UTCEPSS rescore
  30. 2026-08-29 20:43 UTCEG score recompute
  31. 2026-08-28 21:42 UTCEPSS rescore
  32. 2026-08-27 14:25 UTCEPSS rescore
  33. 2026-08-26 15:43 UTCEG score recompute
  34. 2026-08-26 15:06 UTCEG score recompute
  35. 2026-08-26 14:47 UTCEPSS rescore
  36. 2026-08-25 21:26 UTCEG score recompute
  37. 2026-08-25 21:15 UTCEG score recompute
  38. 2026-08-25 21:15 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-72924?
CVE-2026-72924 is a low vulnerability published on August 25, 2026. GitHub CLI (gh) is GitHub's official command line tool. Versions 2.28.0 through 2.97.0 bind the local listener created by gh codespace ports forward to all available network interfaces by default. While port forwarding is active, a service in a Codespace can therefore become reachable through the…
When was CVE-2026-72924 disclosed?
CVE-2026-72924 was first published on August 25, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72924 actively exploited?
CVE-2026-72924 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72924?
CVE-2026-72924 has a CVSS base score of 2.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-72924?
The CVE record for CVE-2026-72924 names the fix: "This issue is fixed in version 2.98.0." The vendor advisories EchelonGraph has for CVE-2026-72924 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-72924

Explore →

Is Your Infrastructure Affected by CVE-2026-72924?

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

Book a Demo →Browse All CVEs