CVE-2026-118668: LangGraph JavaScript custom authentication may permit cross-user Store access
LangGraph deployments (`langgraph-api`) that use JavaScript or TypeScript custom authentication may ignore the namespace rewrite an authorization handler returns for Store requests. A signed-in ordinary user can then read, overwrite, search or delete another user's Store data. Versions from 0.1.2 up to but not including 0.15.0 are affected. Upgrade to 0.15.0.
Published Oct 28, 2026 · Analysis Nov 1, 2026
What an attacker can do
A custom authorization handler can restrict a user to their own data by rewriting the requested Store namespace, for example prefixing it with the user ID. In affected versions, a handler written in JavaScript or TypeScript runs in a separate runtime, and the server did not carry that rewrite back and apply it before the Store operation. The original, unrestricted namespace was used.
The advisory lists all conditions. The deployment uses an affected langgraph-api. It runs JS or TS custom authentication. Its Store handler relies on rewriting the namespace rather than rejecting. The attacker can log in as an ordinary user. Data from several users sits in the same Store.
When those hold, no administrator rights, user interaction or race are needed. The attacker requests another user's namespace and the Store serves it. They can read other users' memories and saved state, overwrite or delete them, and search across them (CWE-639, CWE-863). For agents that keep long-term memory in the Store, that includes whatever users or the agent saved there, and tampering can change later agent behavior.
Python handlers, and JS or TS handlers that reject unauthorized namespaces, are not affected.
Who is affected
The langgraph-api pip package, >= 0.1.2 and < 0.15.0, only when the deployment uses JavaScript or TypeScript custom auth with a Store handler that rewrites namespaces. Check:
pip show langgraph-apiThen read your auth handler for Store actions and see whether it returns a modified namespace or throws on a foreign one.
langgraph-api
- Ecosystem
- PyPI
- Affected
- >= 0.1.2, < 0.15.0
- Fixed in
- 0.15.0
- Check
pip show langgraph-api
How to fix it
Upgrade to langgraph-api 0.15.0 or later:
pip install "langgraph-api>=0.15.0"The server now carries changes made by a JS or TS authorization handler across the runtime boundary and applies them before the Store operation. It validates the resulting namespace after authorization, and rejects the request if a change is malformed or cannot be applied safely.
Workaround if you cannot upgrade: change JS or TS Store handlers so they reject requests for unauthorized namespaces instead of rewriting them. Apply this to every Store action your deployment exposes.
How to tell if you were hit
Review Store access logs and API traces for requests where the namespace in the request belongs to a different user than the authenticated identity. Check for Store items that changed or vanished without an owner action. Run a test with two accounts against a staging copy: have user A request user B's namespace and see whether data returns. Audit your auth handler for any Store action that rewrites rather than rejects.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
LangGraph deployments using JavaScript or TypeScript custom authentication may fail to apply Store authorization changes returned by an authorization handler. In affected deployments, an authenticated user may be able to access Store data outside their authorized namespace.
Required conditions
A deployment is affected only when all of the following conditions apply:
- It uses an affected
langgraph-apiversion. - It runs JavaScript or TypeScript custom authentication.
- Its Store authorization handler relies on rewriting the requested namespace to restrict each user to their own data.
- The attacker can authenticate as an ordinary user.
- Multiple users' data is stored through the affected authorization path.
Python custom authentication handlers are not affected. JavaScript or TypeScript handlers that reject unauthorized namespace requests instead of rewriting them are also not affected.
The attack does not require administrator privileges, user interaction, a race condition, or the bypass of another mitigation.
Impact
An authenticated user may be able to read, overwrite, search, or delete Store data belonging to another user.
Patches
The issue is fixed in langgraph-api version 0.15.0. The server now carries changes made by a JavaScript or TypeScript authorization handler across the runtime boundary and applies them before performing the Store operation. It validates the resulting namespace after authorization and rejects the request if an authorization change is malformed or cannot be applied safely.
Users should upgrade to langgraph-api>=0.15.0.
Workarounds
Deployments that cannot upgrade immediately should change JavaScript or TypeScript Store authorization handlers to reject requests for unauthorized namespaces rather than relying on namespace rewriting.
This workaround must be applied to every Store action exposed by the deployment.
Credited to coinspect-audits.
Questions
- Are Python auth handlers affected?
No. The advisory says Python custom authentication handlers are not affected. Neither are JS or TS handlers that reject unauthorized namespace requests instead of rewriting them.
- Does the attacker need admin rights?
No. An ordinary authenticated user is enough. No user interaction or race condition is involved.
- What does the attacker get?
Read, overwrite, search and delete access to another user's Store data, according to the advisory.
- Is it exploited in the wild?
No source reports exploitation, and it is not in CISA's KEV catalog.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
