Skip to main content
VulnerabilityPublished Updated

CVE-2026-14742: langchain-ai langgraph · Use of Weak Hash

Affects langchain-ai langgraphSource CVE Database V5

0
Compare

Public exploit available · CVSS 2.3 Low.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
langchain-ailanggraphAffected
  • 1.2.0 – 1.2.4
5 affected builds
Fixed in–
npmlangchain-ai/langgraphpkg:npm/langchain-ai/langgraphOther threatsAffected
  • 1.2.0 – 1.2.4
5 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:langchain-ai:langgraph:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A pull request addressing the issue is pending acceptance. Users should monitor the vendor's repository or advisory channels for the official patch. Until then, no specific mitigation steps are documented.

Description

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.

References

Community reviews

Loading reviews…