AI Stack Alert Medium CVE-2026-118667 For AppSec, AI Eng, SOC / IR AI-assisted
LangGraph SDK v3 streaming: unencoded thread_id/assistant_id enables GET path redirection (CVE-2026-118667)
The LangGraph Python SDK v3 streaming client interpolates caller-supplied thread_id and assistant_id into request paths without encoding them at four call sites. Relative path segments can redirect an authenticated GET request to another readable path on the configured server. Affected: langgraph-sdk 0.4.0 through 0.4.5 (fixed in 0.4.6) and langgraph 1.2.3 through 1.2.13 when used with a vulnerable SDK (fixed in 1.2.14).
Why it matters
Applications that pass attacker-controlled text as a streaming thread_id or assistant_id can have the SDK return responses from other server paths to the application. The advisory states the issue provides no write primitive, and the LangGraph Platform is not exposed.
Do this
- Upgrade langgraph-sdk to 0.4.6 or later in all environments that use the v3 streaming client.
- If RemoteGraph is used, upgrade langgraph to 1.2.14 or later, which requires langgraph-sdk>=0.4.6.
- Audit code paths that pass user-supplied values into thread_id or assistant_id for streaming calls, and validate or allowlist these values until upgraded.
- Confirm installed versions with pip show langgraph-sdk langgraph and check lock files for pinned vulnerable versions.
Exploit Clock
Exploitation unlikely (for now)
- EPSS 0.39%
Signals
- NoCISA KEV
- 4.3CVSS
- 0.39%EPSS
- 27/100Priority
- 85%Confidence
Evidence
“Relative path segments can therefore redirect an authenticated GET request to another path on the same configured server.”
“Upgrade `langgraph-sdk` to version 0.4.6 or later.”
“The affected requests are GET operations, so this issue does not provide a write primitive.”
Sources
Affected / related
langgraph-sdk, langgraph, Unencoded path parameter redirection
Published 2026-10-28 21:05 UTC · updated 2026-11-08 02:36 UTC · AI-assisted summary, checked against quoted sources · How we score