LangGraph at a glance
On October 28, 2026, LangChain disclosed that LangGraph deployments using JavaScript or TypeScript custom authentication could ignore Store namespace rewrites, letting an ordinary user read, overwrite or delete another user's data. It is fixed in langgraph-api 0.15.0.
LangGraph: status
- Affected
- langgraph-api 0.1.2 up to 0.15.0 with JavaScript or TypeScript custom authentication whose Store handler rewrites namespaces (CVE-2026-118668)
- langgraph-sdk 0.4.0 up to 0.4.6 and langgraph 1.2.3 up to 1.2.14 (v3 streaming request redirection, CVE-2026-118667)
- Status as of
What changed with LangGraph
On October 28, 2026, LangChain published a GitHub advisory for langgraph-api, the server package that runs LangGraph agent deployments. CVE-2026-118668 scores 8.6 under CVSS 4.0 and affects versions 0.1.2 up to 0.15.0. The Store is LangGraph's long-term memory, where agents keep data such as user preferences and past facts across conversations.
The bug only hits deployments that use JavaScript or TypeScript custom authentication and whose Store authorization handler restricts each user by rewriting the requested namespace. In that setup, the server did not carry the rewrite across from the JavaScript runtime, so an authenticated ordinary user could read, overwrite, search or delete Store data that belonged to someone else. Python handlers, and JavaScript handlers that reject unauthorized namespaces instead of rewriting them, are not affected. Version 0.15.0 applies and validates the rewritten namespace and rejects the request if it cannot.
The same day LangChain also fixed a medium-severity issue, CVE-2026-118667, in which unencoded identifiers in the LangGraph SDK's v3 streaming could redirect authenticated GET requests; it is fixed in langgraph-sdk 0.4.6 and langgraph 1.2.14.
How to fix it: LangGraph
1. Update
Upgrade langgraph-api to 0.15.0 or later, and langgraph-sdk to 0.4.6 and langgraph to 1.2.14 or later.
github.com (opens in a new tab)2. Workaround
If you cannot upgrade, change every JavaScript or TypeScript Store authorization handler to reject requests for namespaces the user does not own instead of rewriting them.
github.com (opens in a new tab)
Instruction for your AI agent
Check Python requirements, lockfiles and deployment images for langgraph-api, langgraph-sdk and langgraph. Propose upgrading langgraph-api below 0.15.0, langgraph-sdk below 0.4.6 and langgraph 1.2.x below 1.2.14. If the project defines JavaScript or TypeScript custom auth handlers for the Store, show the user any that rewrite the namespace instead of rejecting unauthorized requests.
Based on the official guidance linked below. Review it before giving it to an agent that can change your systems.
Advisories
Where to compare LangGraph
Independent leaderboards and official resources for comparing this model yourself. Rankings change often; each site shows its own current data.
Why LangGraph matters for businesses
Agent memory often holds exactly the personal details your clients would least want shared. If you run multi-user LangGraph agents on your own infrastructure with JavaScript auth, upgrade langgraph-api to 0.15.0, or change Store handlers to reject other users' namespaces, and review Store access logs for cross-user reads.
Sources for this story
- LangGraph JavaScript custom authentication may permit cross-user Store access (opens in a new tab)Official
LangChain on GitHub · github.com
- LangGraph: Unencoded identifiers in LangGraph SDK v3 streaming can redirect authenticated GET requests (opens in a new tab)Official
GitHub Advisory Database · github.com
Last verified: . IA Compa summarizes public announcements for business readers. We are not affiliated with the companies mentioned. Always confirm details, pricing, and availability with the official source.
- #security
- #cve
- #langgraph
- #agent-memory
- #authorization