Authorization Flaw in langgraph-sdk (CVE-2026-104873)
Summary
Vulnerability in langgraph-sdk (CVE-2026-104873). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.4.4 or later.
Original description
The description as published by the source.
Impact
What kind of vulnerability is it? Who is impacted?
langgraph-sdk incorrectly applies the actions= argument on resource-scoped authorization decorators, including @auth.on.threads, @auth.on.assistants, and @auth.on.crons.
In affected versions, a decorator such as:
@auth.on.threads(actions=["create"])
async def allow_thread_create(ctx, value):
return None
intended to register a handler for selected actions instead registers that handler for every action on the resource. Because the resource-wide handler is selected before broader fallback handlers, authorization checks implemented in those fallback handlers may not run.
An authenticated user may therefore be able to perform actions the application intended to deny, such as reading, updating, or deleting another user's resource. Exploitability and impact depend on the affected handler's behavior: deployments remain protected if that handler independently enforces the necessary action, ownership, or permission checks for every request it receives.
Only Python deployments using actions= on the affected resource-scoped decorators are affected.
Patches
0.4.4
Workarounds
No.
References
N/A
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-104873 has been found in langgraph-sdk.
Risk of unauthorized operations or information disclosure.
What to do: upgrade langgraph-sdk to 0.4.4 or later.
If unsure, ask your IT team or search "langgraph-sdk CVE-2026-104873" on the vendor's site.
CVE-2026-104873 (langgraph-sdk) — CWE-863
Patched: 0.4.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in langgraph-sdk.
Check the vendor advisory for the affected versions of langgraph-sdk.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.4.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'langgraph-sdk' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'langgraph-sdk' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
langgraph-sdkを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade langgraph-sdk to 0.4.4ステージング環境で 0.4.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。