GHSA-4hm6-w6qq-w73v - LangGraph JavaScript custom authentication may permit cross-user Store access
## 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-api` version.
- 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.
HIGH
Severity & confidence
Source severityhigh
Platform severityhigh
Confidencehigh
Exploitationunknown
CVSS-
Affected
Vendorslanggraph-api
Productslanggraph-api
Reporting sources (2)
GitHub Security Advisories
NIST NVD - National Vulnerability Database
Timeline & provenance
Published2026-10-28T21:09:42
Last updated2026-10-31T21:01:43
Ingested2026-10-28T21:27:23
FreshnessNEAR-REAL-TIME
Threat typeadvisory
Recommended action
Review the advisory and upgrade affected packages to the first patched version.
Next steps
- Identify affected systems in your environment.
- Apply the vendor patch or mitigation guidance.
- Review logs for indicators described in the advisory.
- Follow the affected vendor/product to track updates.
Confidence explanation
Reported by a government or cert-grade source (CISA, NCSC, NVD, ENISA, MSRC).
Source type: vendor ยท Original: GitHub Security Advisories