CVE-2026-104873
Received Received - Intake

Authorization Bypass in LangGraph Python SDK

Vulnerability report for CVE-2026-104873, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-02

Last updated on: 2026-10-02

Assigner: GitHub, Inc.

Description

LangGraph Python SDK is used to connect to running LangGraph API servers, manage assistants, threads and stream runs from Python applications. From 0.1.45 until 0.4.4, the langgraph-sdk resource-scoped authorization decorators @auth.on.threads, @auth.on.assistants, and @auth.on.crons ignore the actions argument and register the selected handler for every action on the resource. Because that wildcard resource handler is selected before broader fallback handlers, an authenticated user may bypass fallback action, ownership, or permission checks and read, update, or delete another user's resource. Only Python deployments using actions on the affected decorators are vulnerable, and a deployment remains protected when the selected handler independently enforces all required checks for every action it receives. This issue is fixed in version 0.4.4.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-02
Last Modified
2026-10-02
Generated
2026-10-03
AI Q&A
2026-10-02
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
langchain-ai langgraph-sdk From 0.1.45 (inc) to 0.4.4 (exc)
langchain-ai langgraph-sdk 0.4.4
langgraph langgraph_python_sdk to 0.4.4 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The vulnerability in the LangGraph Python SDK (versions 0.1.45 to 0.4.3) involves improper handling of resource-scoped authorization decorators. These decorators, such as @auth.on.threads, @auth.on.assistants, and @auth.on.crons, ignore the actions parameter and register handlers for all actions on a resource. This allows authenticated users to bypass fallback checks and perform unauthorized actions like reading, updating, or deleting resources they shouldn't access.

Detection Guidance

To detect this vulnerability, check if your LangGraph SDK version is between 0.1.45 and 0.4.3. Run: pip show langgraph-sdk. If the version falls in this range, the system is vulnerable. Review custom authentication decorators like @auth.on.threads, @auth.on.assistants, and @auth.on.crons for improper handling of the actions parameter.

Inspect logs for unauthorized resource access attempts or actions bypassing permission checks. Enable verbose logging in the SDK to monitor decorator behavior. Verify if fallback authorization checks are being bypassed by testing resource access with different user roles.

Impact Analysis

If you use the affected LangGraph SDK versions with the vulnerable decorators, an authenticated user could bypass authorization checks and access or modify resources belonging to other users. This could lead to data leaks, unauthorized changes, or resource deletion. Only deployments using the actions parameter on these decorators are vulnerable.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, which may violate compliance requirements under GDPR (data protection) and HIPAA (healthcare data privacy). Unauthorized read, update, or delete operations on user resources could result in data breaches or unauthorized disclosures, triggering regulatory penalties or legal consequences.

Mitigation Strategies

Upgrade the LangGraph SDK to version 0.4.4 or later immediately. Run: pip install --upgrade langgraph-sdk==0.4.4. After upgrading, review and update authentication decorators to ensure proper action scoping. Test the system to confirm that unauthorized access attempts are now blocked.

If upgrading is not immediately possible, restrict access to sensitive resources by implementing additional authorization checks at the application level. Monitor logs closely for any signs of exploitation until the upgrade is completed.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-104873. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart