Skip to main content

LangGraph CVE-2026-14742

| EUVDEUVD-2026-41747 LOW
Use of Weak Hash (CWE-328)
2026-07-05 VulDB GHSA-rff8-98wf-8rv4
1.3
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to LangGraph with low-privilege credentials
  2. Delivery
    Analyze task cache key generation behavior via `_freeze`
  3. Exploit
    Engineer inputs to produce colliding `default_cache_key` hash values
  4. Execution
    Submit crafted task to trigger cache lookup collision
  5. Impact
    Receive 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 default_cache_key argument passed to the _freeze function. Attack complexity is rated High (AC:H), meaning reliable hash collision is not trivially achievable and requires deliberate engineering of inputs. No non-default configuration is stated as a prerequisite - any deployment with task caching enabled and multi-user access is potentially in scope. Exploitation is strictly bounded to low confidentiality impact: an attacker cannot modify cached results (VI:N) or cause denial of service (VA:N), and there is no scope change to subsequent systems (SC/SI/SA all N).

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 default_cache_key that collides with a hash value corresponding to another user's cached task result. When the cache lookup resolves the collision, the attacker receives output data from the other task, potentially exposing sensitive intermediate reasoning, tool outputs, or agent memory. A public proof-of-concept detailing this collision approach is available at https://github.com/langchain-ai/langgraph/issues/8009, though the high attack complexity (AC:H) means reliable exploitation requires significant pre-computation or trial-and-error.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

langgraph 1.2.4
langgraph 1.2.1
langgraph 1.2.3
langgraph 1.2.0
langgraph 1.2.2

Affected Packages

euvd langgraph no fix

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

Vendor (VulDB) PRIMARY 1.3 LOW
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
vuln.today AI 3.1 LOW

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.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
High
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
CVSS changed
Jul 05, 2026 - 11:22 NVD
2.3 (LOW) 1.3 (LOW)

DescriptionCVE.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

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Low
niche AI agent orchestration framework, limited broad enterprise footprint
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

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.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +6
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy