CVE-2025-68664

CRITICALNVD 9.39.3
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under NVD CVSS v3. EPSS exploit probability: 2.3%, top 15% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 14%CVSS: 9.3Exploit: NoneExposed: 0

A fix is available — apply it.

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

CVSS v3
9.3
EG Score
9.3(medium)
EPSS
96.2%
KEV
Not listed

Published

December 23, 2025

Last Modified

January 13, 2026

Advisory Details (7)

Auto-updated Jul 17, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
github Patch Available

LangChain serialization injection vulnerability enables secret extraction in dumps/loads APIs · Advisory · langchain-ai/langchain · GitHub

https://github.com/langchain-ai/langchain/security/advisories/GHSA-c67j-w6g6-q2cm
github_release Patch Available

langchain-core==1.2.5

Patch available: langchain-ai/langchain langchain-core==1.2.5

https://github.com/langchain-ai/langchain/releases/tag/langchain-core%3D%3D1.2.5
github_release Patch Available

langchain-core==0.3.81

Patch available: langchain-ai/langchain langchain-core==0.3.81

https://github.com/langchain-ai/langchain/releases/tag/langchain-core%3D%3D0.3.81
github_pr

fix(core): serialization patch

Fix merged in langchain-ai/langchain PR #34458 on 2025-12-23 — awaiting tagged release

https://github.com/langchain-ai/langchain/pull/34458
github_pr Patch Available

fix(core): serialization patch

Patch available: langchain-ai/langchain langchain==1.3.6 (PR #34455 merged 2025-12-22)

https://github.com/langchain-ai/langchain/pull/34455
github_commit

commit d9ec4c5cc789 (langchain-ai/langchain)

Fix landed in langchain-ai/langchain commit d9ec4c5cc789 — awaiting tagged release

https://github.com/langchain-ai/langchain/commit/d9ec4c5cc78960abd37da79b0250f5642e6f0ce6
github_commit Patch Available

commit 5ec0fa69de31 (langchain-ai/langchain)

Patch available: langchain-ai/langchain langchain==1.3.6 (contains commit 5ec0fa69de31)

https://github.com/langchain-ai/langchain/commit/5ec0fa69de31bbe3d76e4cf9cd65a6accb8466c8

Patch Availability(4)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
langchain-core0.0.1 ... 0.3.9 (212 versions)0.3.81

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 02:28 UTCEPSS rescore
  5. 2026-07-19 02:28 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:02 UTCEPSS rescore
  9. 2026-07-16 17:02 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-15 01:59 UTCEPSS rescore
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-08 15:15 UTCEPSS rescore
  20. 2026-07-07 13:46 UTCEPSS rescore
  21. 2026-07-06 07:02 UTCOSV refresh
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-05 02:30 UTCEPSS rescore
  24. 2026-07-05 02:30 UTCEPSS rescore
  25. 2026-07-04 06:31 UTCEPSS rescore
Show 57 more
  1. 2026-07-04 06:31 UTCEPSS rescore
  2. 2026-07-01 15:06 UTCEPSS rescore
  3. 2026-06-30 23:22 UTCEPSS rescore
  4. 2026-06-30 23:22 UTCEPSS rescore
  5. 2026-06-29 14:06 UTCEPSS rescore
  6. 2026-06-29 14:06 UTCEPSS rescore
  7. 2026-06-28 04:56 UTCEPSS rescore
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-24 14:05 UTCEPSS rescore
  13. 2026-06-24 14:04 UTCEPSS rescore
  14. 2026-06-23 21:32 UTCEPSS rescore
  15. 2026-06-21 14:56 UTCEPSS rescore
  16. 2026-06-21 14:56 UTCEPSS rescore
  17. 2026-06-21 01:59 UTCEPSS rescore
  18. 2026-06-21 01:59 UTCEPSS rescore
  19. 2026-06-19 19:25 UTCEPSS rescore
  20. 2026-06-19 19:25 UTCEPSS rescore
  21. 2026-06-18 17:52 UTCEPSS rescore
  22. 2026-06-18 17:52 UTCEPSS rescore
  23. 2026-06-17 18:35 UTCOSV refresh
  24. 2026-06-17 17:53 UTCEPSS rescore
  25. 2026-06-16 17:52 UTCEPSS rescore
  26. 2026-06-15 17:48 UTCEPSS rescore
  27. 2026-06-14 23:18 UTCEPSS rescore
  28. 2026-06-13 23:00 UTCEPSS rescore
  29. 2026-06-13 23:00 UTCEPSS rescore
  30. 2026-06-12 23:12 UTCEPSS rescore
  31. 2026-06-12 23:12 UTCEPSS rescore
  32. 2026-06-11 14:00 UTCEPSS rescore
  33. 2026-06-10 22:18 UTCEPSS rescore
  34. 2026-06-10 13:22 UTCEPSS rescore
  35. 2026-06-08 14:17 UTCEPSS rescore
  36. 2026-06-08 14:17 UTCEPSS rescore
  37. 2026-06-07 15:24 UTCEPSS rescore
  38. 2026-06-07 15:24 UTCEPSS rescore
  39. 2026-06-06 13:47 UTCEPSS rescore
  40. 2026-06-06 13:47 UTCEPSS rescore
  41. 2026-06-05 22:47 UTCEPSS rescore
  42. 2026-06-05 22:46 UTCEPSS rescore
  43. 2026-06-05 06:10 UTCEPSS rescore
  44. 2026-06-05 06:10 UTCEPSS rescore
  45. 2026-06-04 13:12 UTCEPSS rescore
  46. 2026-06-04 13:12 UTCEPSS rescore
  47. 2026-06-02 20:13 UTCEPSS rescore
  48. 2026-06-01 13:51 UTCEPSS rescore
  49. 2026-06-01 13:51 UTCEPSS rescore
  50. 2026-05-31 22:30 UTCEPSS rescore
  51. 2026-05-31 22:30 UTCEPSS rescore
  52. 2026-05-31 00:16 UTCEPSS rescore
  53. 2026-05-31 00:16 UTCEPSS rescore
  54. 2026-05-29 17:01 UTCEG score recompute
  55. 2026-05-29 17:01 UTCVendor advisory
  56. 2026-05-29 13:44 UTCEPSS rescore
  57. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52514
    First seen Apr 29, 2026

    LangChain Core 1.2.4 - SSTI/RCE

    Open source ↗
  • GitHub PoCAk-cybe/CVE-2025-68664-LangGrinch-PoC
    First seen Dec 27, 2025

    A testing framework to identify and demonstrate deserialization vulnerabilities in LangChain Core (<0.3.81). Educational use only

    Open source ↗

Frequently asked(5)

What is CVE-2025-68664?
CVE-2025-68664 is a critical vulnerability published on December 23, 2025. LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form…
When was CVE-2025-68664 disclosed?
CVE-2025-68664 was first published in the National Vulnerability Database on December 23, 2025, with the most recent update on January 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-68664 actively exploited?
CVE-2025-68664 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-68664?
CVE-2025-68664 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2025-68664?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68664, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68664

Explore →

Is Your Infrastructure Affected by CVE-2025-68664?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.