Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to LangGraph with low-privilege credentials
-
DeliveryAnalyze task cache key generation behavior via `_freeze`
-
ExploitEngineer inputs to produce colliding `default_cache_key` hash values
-
ExecutionSubmit crafted task to trigger cache lookup collision
-
ImpactReceive cached output belonging to another task or user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Irreversible hash functions
|
| Exploitation Conditions | Exploitation requires a valid low-privilege authenticated session on the target LangGraph deployment running version 1.2.4 or earlier (CVSS PR:L confirmed). The attacker must have the ability to submit tasks that interact with the Task Result Cache component and influence the |
| Impact | Real-world risk is low despite the existence of a public proof-of-concept. The CVSS 4.0 vector AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N confirms three distinct risk-reducing factors: authentication is required (PR:L eliminates unauthenticated mass exploitation), attack complexity is high (AC:H - collision engineering is non-trivial), and impact is bounded to low confidentiality disclosure only with no integrity or availability dimensions. The E:P modifier in the provided vector acknowledges the POC, but the base score of 2.3 appropriately reflects constrained exploitability. No EPSS data was provided; KEV status is absent, meaning CISA has not observed active exploitation. The patch exists only as an unmerged pull request (PR #8069), so no vendor-released fixed version is confirmed yet. This is a monitoring priority, not an emergency response item, for most organizations. |
| Exploit ScenarioDerived | A low-privilege authenticated user on a shared LangGraph deployment crafts task inputs specifically engineered to produce a |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 05, 2026
Weak hashing in LangGraph's Task Result Cache exposes low-privilege authenticated users to hash collision attacks that can leak cached task results across isolation boundaries. All LangGraph versions through 1.2.4 are affected via the _freeze function in libs/langgraph/langgraph/_internal/_cache.py. A public proof-of-concept is disclosed at GitHub issue #8009, though the CVSS 4.0 score of 2.3 and AC:H rating reflect genuinely high exploitation difficulty; this is not listed in CISA KEV and no active exploitation has been reported.
RemediationAI
No vendor-released patched version has been confirmed at time of analysis - the fix exists as a pending pull request at https://github.com/langchain-ai/langgraph/pull/8069 awaiting merge. Organizations should monitor the LangGraph GitHub repository (https://github.com/langchain-ai/langgraph/) and upgrade as soon as a patched release is published. As an interim compensating control, restrict authenticated access to LangGraph deployments to the minimum set of trusted users, since exploitation requires at least low-privilege credentials (PR:L); this reduces the attacker pool without disabling functionality. Where task result caching is not required for correctness or performance, disabling the cache entirely eliminates the vulnerable code path, though this will increase compute cost for repeated task evaluations. Do not rely on network-perimeter controls alone, as the vulnerability is network-accessible by design.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
LangGraph (CPE: cpe:2.3:a:langchain-ai:langgraph) is a Python framework for building stateful, multi-actor AI agent workflows on top of the LangChain ecosystem. The vulnerable component is the _freeze function in libs/langgraph/langgraph/_internal/_cache.py, which generates cache keys for task results using the default_cache_key argument. CWE-328 (Use of Weak Hash) identifies the root cause: the hash algorithm chosen for key generation is cryptographically insufficient, meaning an attacker who can influence or predict inputs can engineer hash collisions. In a task result cache context, a successful collision would cause the cache to serve one user's or task's results to another requester, constituting a cross-task information disclosure.
Know when Langgraph gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Network-reachable but requires authenticated low-privilege access (PR:L) and high-complexity hash collision (AC:H); impact is limited to low confidentiality with no integrity or availability dimensions.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
1DescriptionCVE.org
A vulnerability was determined in langchain-ai langgraph up to 1.2.4. The affected element is the function _freeze of the file libs/langgraph/langgraph/_internal/_cache.py of the component Task Result Cache. This manipulation of the argument default_cache_key causes use of weak hash. The attack is possible to be carried out remotely. The complexity of an attack is rather high. The exploitability is described as difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Incorrect authorization in the LangGraph Python SDK (langgraph-sdk) versions 0.1.45 through 0.4.3 lets an authenticated
Unsafe deserialization in LangGraph SQLite Checkpoint's JsonPlusSerializer (versions 4.1.0 and prior) allows arbitrary P
LangGraph SQLite Checkpoint versions 1.0.9 and prior are vulnerable to unsafe deserialization of msgpack-encoded objects
Cross-namespace data exposure in the Postgres- and SQLite-backed LangGraph stores (langgraph-checkpoint-postgres before
Path traversal in the LangGraph Python SDK (langgraph-sdk 0.4.0 through 0.4.5, and langgraph 1.2.3 through 1.2.13 via Re
LangGraph CLI versions 0.4.15 through 0.4.31 disclose the short-lived LangSmith registry push token in verbose output: `
EUVD-2026-41747
GHSA-rff8-98wf-8rv4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB