LangGraph Python SDK is used to connect to running LangGraph API servers, manage assistants, threads and stream runs from Python applications. From langgraph-sdk 0.4.0 until 0.4.6, and from langgraph 1.2.3 until 1.2.14 when RemoteGraph v3 streaming uses an affected langgraph-sdk version, the synchronous and asynchronous v3 stream get_tree and _fetch_state helpers interpolate caller-controlled assistant_id and thread_id values into authenticated GET request paths without using _quote_path_param. Relative path segments can therefore be normalized into another readable path on the configured server while retaining authentication headers. This issue is fixed in langgraph-sdk 0.4.6 and langgraph 1.2.14.
CVE-2026-118667
MEDIUMPre-NVD 4.34.3Trending — 5 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 4.3 from GitHub Security Advisory (severity: MODERATE) published 2026-10-28. A secondary CVSS source baseline 4.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-112474 (ENISA EUVD) · GHSA-3fx2-cqw9-xr3c (GitHub Security Advisories)Source: ENISA EUVD
4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.3Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 4.3
- EG Score
- 4.3MEDIUMhigh confidence
- EG Risk
- 20EG Risk 20/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity43% × 45%Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 33rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 28, 2026
Last Modified
October 29, 2026
Advisory Details (5)
Auto-updated Oct 29, 2026Patch available. Sources: github_release, github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)
Unencoded identifiers in LangGraph SDK v3 streaming can redirect authenticated GET requests · Advisory · langchain-ai/langgraph · GitHub
https://github.com/langchain-ai/langgraph/security/advisories/GHSA-3fx2-cqw9-xr3cGitHub release Patch Available
langgraph-sdk==0.4.6
Patch available: langchain-ai/langgraph sdk==0.4.6
https://github.com/langchain-ai/langgraph/releases/tag/sdk%3D%3D0.4.6GitHub release Patch Available
langgraph==1.2.14
Patch available: langchain-ai/langgraph 1.2.14
https://github.com/langchain-ai/langgraph/releases/tag/1.2.14GitHub pull request Patch Available
fix(sdk-py): percent-encode thread_id and assistant_id in thread stream requests
Patch available: langchain-ai/langgraph sdk==0.4.6 (PR #9213 merged 2026-10-06)
https://github.com/langchain-ai/langgraph/pull/9213GitHub commit Patch Available
commit d89c7e100ec6 (langchain-ai/langgraph)
Patch available: langchain-ai/langgraph sdk==0.4.6 (contains commit d89c7e100ec6)
https://github.com/langchain-ai/langgraph/commit/d89c7e100ec6fc1512544d23b0a7c5169699ef3eVendor Advisories for CVE-2026-118667(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | langgraph @ 1.2.14 (fixes >= 1.2.3, < 1.2.14) | — | ghsa |
| pip | langgraph-sdk @ 0.4.6 (fixes >= 0.4.0, < 0.4.6) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 1 ecosystem)
PyPI(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| langgraph | 1.2.10 ... 1.2.9 (11 versions) |
| — |
| langgraph-sdk | 0.4.0 ... 0.4.5 (6 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 07:59 UTCGHSA enrichmentGHSA-3fx2-cqw9-xr3c · GitHub severity MODERATE · GitHub CVSS 4.3
- 2026-11-01 07:59 UTCEG score recompute
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-29 19:26 UTCEG score recompute
- 2026-10-29 18:37 UTCEG score recompute
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-28 21:28 UTCEG score recompute
- 2026-10-28 21:02 UTCEG score recomputeFirst assessed: 4.3 MEDIUM
- 2026-10-28 21:01 UTCENISA EUVD ID recordedEUVD-2026-112474 · Source: ENISA EUVD
- 2026-10-28 20:58 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
3 shownPyPI:langgraph · PyPI:langgraph-sdk
Frequently asked(5)
What is CVE-2026-118667?
CVE-2026-118667 is a medium-severity vulnerability; its CVE record was published on October 28, 2026. LangGraph Python SDK is used to connect to running LangGraph API servers, manage assistants, threads and stream runs from Python applications. From langgraph-sdk 0.4.0 until 0.4.6, and from langgraph 1.2.3 until 1.2.14 when RemoteGraph v3 streaming uses an affected langgraph-sdk version, the…
When was the CVE record for CVE-2026-118667 published?
The CVE record for CVE-2026-118667 was published on October 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 29, 2026; the record at its source may have been updated since.
Is CVE-2026-118667 actively exploited?
CVE-2026-118667 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118667?
CVE-2026-118667 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-118667?
A fix for CVE-2026-118667 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-118667 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-118667
Is Your Infrastructure Affected by CVE-2026-118667?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.