Path Traversal in langgraph-sdk (CVE-2026-48776)
Summary
Path traversal in langgraph-sdk (CVE-2026-48776). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.3.15 or later.
Original description
The description as published by the source.
Summary
langgraph-sdk constructs HTTP request paths for resource operations by interpolating caller-supplied identifier values into URL templates. Without sanitization of those values, identifiers that contain characters with special meaning in URL paths could cause the resulting request to address a different resource (and potentially a different resource type) than the SDK method's call site indicates. In deployments where the SDK receives identifier values that originate from untrusted sources, this could result in unintended access, modification, or deletion of resources beyond the calling user's authorization scope.
This issue is most consequential in deployments that:
- forward end-user-supplied values directly into SDK identifier parameters without first validating them against an expected format (such as a UUID), and
- rely on URL-prefix-based authorization at an upstream layer (reverse proxy, edge gateway, WAF), where the authorization decision is made on the SDK call's intended path rather than on the final delivered request path.
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources.
Affected users / systems
You may be affected if you:
- use
langgraph-sdk(Python) to address resources by identifier, and - pass identifier values into SDK methods that originate from end-user input, untrusted third-party caller…
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-48776 has been found in langgraph-sdk.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: upgrade langgraph-sdk to 0.3.15 or later.
If unsure, ask your IT team or search "langgraph-sdk CVE-2026-48776" on the vendor's site.
CVE-2026-48776 (langgraph-sdk) — CWE-22 / CVSS v3 4.2
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.3.15 — 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.
Path traversal (CWE-22) exists in langgraph-sdk.
Check the vendor advisory for the affected versions of langgraph-sdk.
Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure.
Update to 0.3.15.
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.3.15ステージング環境で 0.3.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web pypi.org