CVE-2026-48776

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% 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, nvd
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

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

LangGraph Python SDK is used to connect to running LangGraph API servers, manage assistants, threads and stream runs from Python applications. Versions 0.3.14 and prior have unsafe URL path construction through unsanitized caller-supplied identifier values used in HTTP request paths for resource operations. Without sanitization of those values, identifiers that contain characters with special meaning in URL paths could cause the resulting request to address a different resource (and potentially a different resource type) than the SDK method's call site indicates. In deployments where the SDK receives identifier values that originate from untrusted sources, this could result in unintended access, modification, or deletion of resources beyond the calling user's authorization scope. This issue is most consequential in deployments that forward end-user-supplied values directly into SDK identifier parameters without first validating them against an expected format (such as a UUID), and rely on URL-prefix-based authorization at an upstream layer (reverse proxy, edge gateway, WAF), where the authorization decision is made on the SDK call's intended path rather than on the final delivered request path. The issue has been fixed in version 0.3.15.

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

Published

June 17, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
Patch available. Sources: github_release, github.
github Patch Available

Unsafe URL path construction in LangGraph SDK · Advisory · langchain-ai/langgraph · GitHub

https://github.com/langchain-ai/langgraph/security/advisories/GHSA-w39p-vh2g-g8g5
github_release Patch Available

langgraph-sdk==0.3.15

Patch available: langchain-ai/langgraph sdk==0.3.15

https://github.com/langchain-ai/langgraph/releases/tag/sdk%3D%3D0.3.15

Vendor Advisories for CVE-2026-48776(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 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFixed inDependents
langgraph0.0.10 ... 0.3.9 (175 versions)0.3.15—
langgraph-sdk0.1.0 ... 0.3.9 (96 versions)0.3.15—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 51× 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 105 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48776?
CVE-2026-48776 is a critical vulnerability published on June 17, 2026. LangGraph Python SDK is used to connect to running LangGraph API servers, manage assistants, threads and stream runs from Python applications. Versions 0.3.14 and prior have unsafe URL path construction through unsanitized caller-supplied identifier values used in HTTP request paths for resource…
When was CVE-2026-48776 disclosed?
CVE-2026-48776 was first published in the National Vulnerability Database on June 17, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48776 actively exploited?
CVE-2026-48776 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 88.1% of all scored CVEs.
What is the CVSS score of CVE-2026-48776?
CVE-2026-48776 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-48776?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48776, 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-48776

Explore →

Is Your Infrastructure Affected by CVE-2026-48776?

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

Start Free Scan →Browse All CVEs