CVE-2026-48776
MediumCVSS 4.2Exploitation Probability (EPSS)
Low risk8th percentile — higher than 8% of all known CVEs
Summary
Vulnerability in LangGraph Python SDK (versions up to 0.3.14) due to unsafe URL path construction from unsanitized caller-supplied identifiers. Identifiers with special URL characters can cause HTTP requests to target different resources, potentially leading to unauthorized access, modification, or deletion.
Risk Assessment
The risk is bypassing URL-prefix-based authorization (e.g., in reverse proxies, WAF) when the application passes unsanitized end-user input directly as SDK identifiers. This may result in access to resources beyond the caller's authorization scope.
Recommendation
Immediately upgrade LangGraph Python SDK to version 0.3.15 or later. Additionally, validate identifiers against expected formats (e.g., UUID) before passing them to the SDK, and do not rely solely on URL-prefix-based authorization.
Original NVD description (English source)
LangGraph Python SDK is used to connect to running LangGraph API servers, manage assistants, threads and stream runs from Python applications. Versions 0.3.14 and prior have unsafe URL path construction through unsanitized caller-supplied identifier values used in HTTP request paths for resource operations. 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. The issue has been fixed in version 0.3.15.