CVE-2026-59831

MEDIUMPre-NVD 4.44.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. 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
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.4Exploit: None knownExposed: 0

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

GitHub CLI (gh) is GitHub’s official command line tool. From 2.10.0 through 2.95.0, connecting to a malicious Codespace with gh codespace jupyter can allow command execution because the command opens a JupyterLab URL supplied by a process inside the Codespace without validating that it is a loopback HTTP or HTTPS address, allowing a crafted vscode:// or vscode-insiders:// URL to be handed to VS Code. This issue is fixed in version 2.96.0.

CVSS v3
4.4
EG Score
4.4(medium)
EG Risk
20(Track)
EG Risk 20/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
Severity44% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

July 9, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Jul 9, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Connecting to a malicious Codespace via `gh codespace jupyter` could allow command execution on the user's computer · Advisory · cli/cli · GitHub

https://github.com/cli/cli/security/advisories/GHSA-8cg3-r6g9-fpg2
github_release Patch Available

GitHub CLI 2.96.0

Patch available: cli/cli v2.96.0

https://github.com/cli/cli/releases/tag/v2.96.0
github_commit

commit b300f2ec7ec9 (cli/cli)

Fix landed in cli/cli commit b300f2ec7ec9 — awaiting tagged release

https://github.com/cli/cli/commit/b300f2ec7ec9dc9addc39b2ad88c54097ded7ca0

Vendor Advisories for CVE-2026-59831(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 rangeFixed inDependents
gh2.23.0+dfsg1-1 ... 2.46.0-4 (16 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
gh2.46.0-3, 2.46.0-4——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 79× 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.

Showing the most recent 100 of 112 total refreshes for this CVE.

  1. 2026-08-26 03:47 UTCEG score recompute
  2. 2026-08-26 03:47 UTCVendor advisory
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-25 03:27 UTCEG score recompute
  5. 2026-08-24 03:57 UTCVendor advisory
  6. 2026-08-23 03:14 UTCEG score recompute
  7. 2026-08-23 03:14 UTCVendor advisory
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 03:35 UTCEG score recompute
  10. 2026-08-22 03:35 UTCVendor advisory
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 03:46 UTCEG score recompute
  13. 2026-08-21 03:46 UTCVendor advisory
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-20 03:39 UTCEG score recompute
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-19 03:54 UTCEG score recompute
  18. 2026-08-19 03:54 UTCVendor advisory
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-18 03:44 UTCEG score recompute
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-17 04:06 UTCEG score recompute
  23. 2026-08-17 04:06 UTCVendor advisory
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 04:36 UTCEG score recompute
Show 75 more
  1. 2026-08-16 04:36 UTCVendor advisory
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 05:06 UTCEG score recompute
  4. 2026-08-15 05:06 UTCVendor advisory
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 05:35 UTCEG score recompute
  7. 2026-08-14 05:35 UTCVendor advisory
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 06:05 UTCEG score recompute
  10. 2026-08-13 06:05 UTCVendor advisory
  11. 2026-08-12 13:51 UTCEPSS rescore
  12. 2026-08-12 06:34 UTCEG score recompute
  13. 2026-08-12 06:34 UTCVendor advisory
  14. 2026-08-11 07:04 UTCEG score recompute
  15. 2026-08-11 07:04 UTCVendor advisory
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 07:33 UTCEG score recompute
  18. 2026-08-09 13:46 UTCEPSS rescore
  19. 2026-08-09 08:04 UTCEG score recompute
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-08 08:34 UTCEG score recompute
  22. 2026-08-08 08:34 UTCVendor advisory
  23. 2026-08-07 09:04 UTCEG score recompute
  24. 2026-08-07 09:04 UTCVendor advisory
  25. 2026-08-06 13:47 UTCEPSS rescore
  26. 2026-08-06 09:35 UTCEG score recompute
  27. 2026-08-06 09:35 UTCVendor advisory
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-05 10:05 UTCEG score recompute
  30. 2026-08-05 10:05 UTCVendor advisory
  31. 2026-08-04 15:10 UTCEPSS rescore
  32. 2026-08-04 10:39 UTCEPSS rescore
  33. 2026-08-04 10:11 UTCEG score recompute
  34. 2026-08-03 10:36 UTCEPSS rescore
  35. 2026-08-02 10:08 UTCEG score recompute
  36. 2026-08-02 10:08 UTCVendor advisory
  37. 2026-08-02 02:27 UTCEPSS rescore
  38. 2026-08-01 10:38 UTCEG score recompute
  39. 2026-08-01 10:38 UTCVendor advisory
  40. 2026-08-01 04:16 UTCEPSS rescore
  41. 2026-07-31 11:06 UTCEG score recompute
  42. 2026-07-31 11:06 UTCVendor advisory
  43. 2026-07-30 16:28 UTCEPSS rescore
  44. 2026-07-30 11:16 UTCEG score recompute
  45. 2026-07-30 11:16 UTCVendor advisory
  46. 2026-07-30 01:30 UTCEPSS rescore
  47. 2026-07-30 01:30 UTCEPSS rescore
  48. 2026-07-29 11:45 UTCEG score recompute
  49. 2026-07-29 11:45 UTCVendor advisory
  50. 2026-07-28 15:37 UTCEPSS rescore
  51. 2026-07-28 12:15 UTCEG score recompute
  52. 2026-07-28 12:15 UTCVendor advisory
  53. 2026-07-27 14:14 UTCEPSS rescore
  54. 2026-07-27 11:45 UTCEG score recompute
  55. 2026-07-26 14:54 UTCEPSS rescore
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-26 12:15 UTCEG score recompute
  58. 2026-07-26 12:15 UTCVendor advisory
  59. 2026-07-25 14:18 UTCEPSS rescore
  60. 2026-07-25 14:18 UTCEPSS rescore
  61. 2026-07-24 14:18 UTCEPSS rescore
  62. 2026-07-24 14:18 UTCEPSS rescore
  63. 2026-07-23 14:18 UTCEPSS rescore
  64. 2026-07-23 14:18 UTCEPSS rescore
  65. 2026-07-23 03:21 UTCEG score recompute
  66. 2026-07-22 14:08 UTCEPSS rescore
  67. 2026-07-22 14:08 UTCEPSS rescore
  68. 2026-07-21 15:25 UTCEPSS rescore
  69. 2026-07-21 15:25 UTCEPSS rescore
  70. 2026-07-20 17:08 UTCEPSS rescore
  71. 2026-07-19 14:31 UTCEPSS rescore
  72. 2026-07-19 02:29 UTCEPSS rescore
  73. 2026-07-18 10:04 UTCEPSS rescore
  74. 2026-07-16 19:30 UTCVendor advisory
  75. 2026-07-16 17:03 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59831?
CVE-2026-59831 is a medium vulnerability published on July 9, 2026. GitHub CLI (gh) is GitHub’s official command line tool. From 2.10.0 through 2.95.0, connecting to a malicious Codespace with gh codespace jupyter can allow command execution because the command opens a JupyterLab URL supplied by a process inside the Codespace without validating that it is a…
When was CVE-2026-59831 disclosed?
CVE-2026-59831 was first published in the National Vulnerability Database on July 9, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59831 actively exploited?
CVE-2026-59831 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 75.0% of all scored CVEs.
What is the CVSS score of CVE-2026-59831?
CVE-2026-59831 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-59831?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59831, 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-59831

Explore →

Is Your Infrastructure Affected by CVE-2026-59831?

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

Start Free Scan →Browse All CVEs