Live › vulnerability › CVE-2026-118667
Go to dashboardThe LangGraph Python SDK v3 streaming client puts caller-supplied thread_id and assistant_id values into request paths without encoding them, so relative path segments can redirect an authenticated GET to another readable path on the same server. An attacker who controls those identifiers can read another response on the configured server, and can control the query string through thread_id, but cannot write.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 21:07 UTC, 0h before NVD. All times on this page are UTC.
Applications using the LangGraph Python SDK v3 streaming client that pass attacker-controlled text as a streaming thread_id or assistant_id are exposed, along with RemoteGraph v3 streaming users on affected SDK versions. The LangGraph Platform is not exposed. Teams that only use trusted, server-generated identifiers, or that do not use v3 streaming, can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| langgraph-sdk | pypi | >= 0.4.0, < 0.4.6 | 0.4.6 |
| langgraph | pypi | >= 1.2.3, < 1.2.14 | 1.2.14 |
pip show langgraph-sdk and check whether the version is 0.4.0 through 0.4.5pip show langgraph and check whether the version is 1.2.3 through 1.2.13 with a vulnerable langgraph-sdklanggraph-sdk to 0.4.6 or laterlanggraph to 1.2.14 or later if you use RemoteGraph, which requires langgraph-sdk>=0.4.6Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The LangGraph Python SDK v3 streaming client interpolates caller-supplied thread_id and assistant_id values into request paths without encoding them at four synchronous and asynchronous call sites. Relative path segments can therefore redirect an authenticated GET request to another path on the same configured server.
The affected get_tree and _fetch_state implementations build request paths from raw identifiers rather than passing each identifier through the SDK's existing _quote_path_param helper. HTTP path normalization can collapse values containing relative segments before dispatch while retaining the client's authentication headers.
langgraph-sdk versions 0.4.0 through 0.4.5 are affected. The v3 stream module is not present in the 0.3.x release line.
RemoteGraph v3 streaming in langgraph 1.2.3 and later is also affected when used with a vulnerable langgraph-sdk version. It passes config["configurable"]["thread_id"] into threads.stream(...), and its dependency range permits affected SDK versions.
An application is affected only if it passes attacker-controlled text as a streaming thread_id or assistant_id. In that configuration, an attacker may select another readable path on the configured server and cause the SDK to return that response to the application. Through thread_id, the attacker can also control the query string, for example by targeting /store/items?namespace=...&key=...; assistant_id controls only the path. The affected requests are GET operations, so this issue does not provide a write primitive.
The LangGraph Platform is not exposed to this issue.
Upgrade langgraph-sdk to version 0.4.6 or later. The fix encodes assistant_id in get_tree and thread_id in _fetch_state with _quote_path_param in both synchronous and asynchronous stream modules.
If you use RemoteGraph, also upgrade langgraph to version 1.2.14 or later, which requires langgraph-sdk>=0.4.6.
This page as .md · .json · in your agent: get_signal("CVE-2026-118667")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.