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% (23rd 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
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/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
Severity44% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. 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

July 9, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Jul 9, 2026
Patch available. Sources: github_commit, github_release, github.
githubMentions a patch (unverified)

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 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(1)

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

Data Freshness Timeline

(refreshed 6× 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.

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

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

Related CVEs(same product + 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 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.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59831?
CVE-2026-59831 has a CVSS base score of 4.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59831?
A fix for CVE-2026-59831 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59831 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-59831

Explore →

Is Your Infrastructure Affected by CVE-2026-59831?

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

Book a Demo →Browse All CVEs