CVE Intelligence
Low Cryptography exploit reference

CVE-2026-14742 — langchain-ai langgraph Task Result Cache _cache.py _freeze weak hash

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.

Published Jul 5, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Langchain-ai
Langgraph
CVSS base
3.1
Low · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Langchain-ai Langgraph).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (cryptography), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Langchain-ai Langgraph version 1.2.0version 1.2.1version 1.2.2version 1.2.3version 1.2.4 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
2.3 CVSS 4.0 Low — — VulDB via CVE Program (cve.org) e CISA ADP
1.3 CVSS 4.0 Low — — cna@vuldb.com via NIST National Vulnerability Database
3.1 CVSS 3.1 Low 1.6 1.4 cna@vuldb.com via NIST National Vulnerability Database
3.1 CVSS 3.1 Low — — VulDB via CVE Program (cve.org) e CISA ADP
3.1 CVSS 3.0 Low — — VulDB via CVE Program (cve.org) e CISA ADP
2.1 CVSS 2.0 Low 3.9 2.9 cna@vuldb.com via NIST National Vulnerability Database
2.1 CVSS 2.0 Low — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N (score shown at the top: cna@vuldb.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-327 · Use of a Broken or Risky Cryptographic Algorithm

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Check TLS negotiations and unexpected certificates in the component’s traffic.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · langchain-ai/langgraph
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • CVSS changed · 3.1
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Jul 5, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

7 on the record

Elsewhere on this site

Langchain-ai
every CVE for this vendor
Cryptography
same class
CWE-327
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-104873 LangGraph SDK custom auth silently ignores actions= on resource decorators 13d
  • Medium CVE-2026-71433 LangGraph: Namespace prefix matching crosses segment boundaries in Postgres and SQLite stores Aug 6, 2026
  • Medium CVE-2026-48775 LangGraph Checkpoint: Unsafe JSON deserialization in checkpoint loading Jun 16, 2026
  • High CVE-2026-28277 LangGraph: Unsafe msgpack deserialization in LangGraph checkpoint loading Mar 5, 2026
  • High CVE-2025-67644 LangGraph SQLite Checkpoint is vulnerable to SQL Injection via metadata filter key in checkpointer list method Dec 10, 2025
  • High CVE-2025-64439 LangGraph Checkpoint affected by RCE in "json" mode of JsonPlusSerializer Nov 7, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-14742 is "langchain-ai langgraph Task Result Cache _cache.py _freeze weak hash", rated Low. It affects Langgraph (Langchain-ai); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.1 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.