Skip to main content
VulnerabilityPublished

CVE-2025-68664: langchain · Deserialization of Untrusted Data

Affects langchainSource CVE Database V5

0
Compare

Public exploit available (Exploit-DB) · 42% EPSS · CVSS 9.3 Critical : upgrade to 1.2.5 or 0.3.81 as a priority.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
42.9% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.2.5, 0.3.81
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 23 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

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

    Not in CISA KEV and no source reports exploitation

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

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by GitHub, Inc.

    , 23 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 9 minutes after disclosure

  4. First Exploit-DB entry (opens in a new tab)

    LangChain Core 1.2.4 - SSTI/RCE

    , 127 days after disclosure

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

What to do

Upgrade langchain to 1.2.5 or 0.3.81.

Affected software

ProductAffectedFixed in
PyPIlangchainpkg:pypi/langchainOther threatsAffected
  • <0.3.81
  • <1.2.5
Fixed in
  • 0.3.81
  • 1.2.5

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

AI-suggested

  1. Immediately upgrade all LangChain deployments to version 0.3.81 or 1.2.5 or later, where the vulnerability is patched.
  2. Audit all application components that use LangChain serialization/deserialization to ensure they do not process untrusted or user-supplied data without validation.
  3. Implement strict input validation and sanitization to detect and reject dictionaries containing the 'lc' key or other suspicious serialized structures before deserialization.
  4. Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with custom rules to monitor and block anomalous deserialization payloads targeting LangChain endpoints.
  5. Restrict network exposure of services using LangChain serialization to trusted internal networks or authenticated users only.
  6. Conduct thorough code reviews and penetration testing focused on deserialization flows in AI applications.
  7. Monitor security advisories and threat intelligence feeds for any emerging exploits related to this CVE.
  8. Educate developers and DevOps teams about secure deserialization practices and the risks associated with untrusted data processing.

Description

CVE-2025-68664 is a critical deserialization vulnerability in the LangChain framework versions prior to 0.3.81 and 1.2.5. The vulnerability arises because LangChain's dumps() and dumpd() serialization functions do not properly escape dictionaries containing the 'lc' key, which is internally used to mark serialized objects. Malicious actors can craft user-controlled data with this key to trigger unsafe deserialization, leading to potential remote code execution or unauthorized data manipulation. The vulnerability has a CVSS score of 9.3, indicating high severity with network attack vector, no privileges or user interaction required, and a scope change. European organizations using vulnerable LangChain versions in AI or agent-based applications face risks of confidentiality breaches and integrity violations.

References

Community reviews

Loading reviews…