CVE-2026-118668 · GHSA-4hm6-w6qq-w73v
LangGraph JavaScript custom authentication may permit cross-user Store access
- Risk score
- 57/100
- CVSS
- 8.6 v4.0
- Published
- 28 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- langgraph-api implements the LangGraph API for rapid development and testing. From 0.1.2 until 0.15.0, JavaScript or TypeScript custom authentication Store authorization handlers can return a rewritten namespace that is not carried across the runtime boundary and applied before the Store operation. An authenticated us…
- Affected
- langgraph-api (pip) >= 0.1.2, < 0.15.0
- Fix
- Upgrade langgraph-api to 0.15.0 or later.
- Exploitation
- No known exploitation
Story map
At a glance
langgraph-api: Yellow, plan it in. langgraph-api implements the LangGraph API for rapid development and testing. From 0.1.2 until 0.15.0, JavaScript or TypeScript custom authentication Store authorization handlers can return a rewritten namespace that is not carried across the runtime boundary and applied before the Store operation. An authenticated us…
The flaws
- CVE-2026-118668: LangGraph JavaScript custom authentication may permit cross-user Store access (CVSS 8.6)
- CVE-2026-55236: Incomplete assistant authorization in LangGraph Server run creation (CVSS 5.9)
- CVE-2026-55235: Relative webhook targets in LangGraph Server can reach in-process routes without authentication (CVSS 5.9)
The fix
Upgrade langgraph-api: 0.15.0 or later on your release line
Who is exposed: langgraph-api (pip) >= 0.1.2, < 0.15.0
Where it stands
- No known exploitation
Connects to
- Same weakness: Authorisation bypass (CWE-639). 261 other warnings in 30 days
Why it is Yellow
- CVSS 8.6 high
- On your watchlist: PyPI
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| langgraph-api | pip | >= 0.1.2, < 0.15.0 | 0.15.0 |
References
Original description
langgraph-api implements the LangGraph API for rapid development and testing. From 0.1.2 until 0.15.0, JavaScript or TypeScript custom authentication Store authorization handlers can return a rewritten namespace that is not carried across the runtime boundary and applied before the Store operation. An authenticated user can therefore access another user's Store namespace when a deployment relies on namespace rewriting for isolation, allowing unauthorized reads, overwrites, searches, or deletions. Python custom authentication and handlers that reject unauthorized namespaces instead of rewriting them are not affected. This issue is fixed in version 0.15.0.
Last activity 28 Oct 2026. Patch Forecast updates every hour.