LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. 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 @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3
CVE-2025-68665
This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.8%, top 48% 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).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.6
- EG Score
- 8.6(medium)
- EG Risk
- 70(Attend)EG Risk 70/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity86% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 55%
- KEV
- Not listed
Published
December 23, 2025
Last Modified
January 13, 2026
Advisory Details (3)
Auto-updated Aug 8, 2026LangChain serialization injection vulnerability enables secret extraction · Advisory · langchain-ai/langchainjs · GitHub
https://github.com/langchain-ai/langchainjs/security/advisories/GHSA-r399-636x-v7f6[email protected]
Patch available: langchain-ai/langchainjs [email protected]
https://github.com/langchain-ai/langchainjs/releases/tag/langchain%401.2.3commit e5063f9c6e99 (langchain-ai/langchainjs)
Patch available: langchain-ai/langchainjs @langchain/[email protected] (contains commit e5063f9c6e99)
https://github.com/langchain-ai/langchainjs/commit/e5063f9c6e9989ea067dfdff39262b9e7b6aba62Vendor Advisories for CVE-2025-68665(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rhoai/odh-llama-stack-core-rhel9:1771415661 | 2026-03-04 | redhat |
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
(2 across 1 ecosystem)
npm(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| langchain | — | 0.3.37 | — |
| @langchain/core | — | 0.3.80 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 27× 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.
Showing the most recent 100 of 154 total refreshes for this CVE.
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-15 03:10 UTCEPSS rescore
- 2026-09-14 05:50 UTCOSV refresh
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:00 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-26 14:45 UTCEPSS rescore
- 2026-08-26 07:13 UTCOSV refresh
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-24 14:16 UTCEPSS rescore
- 2026-08-23 00:18 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:46 UTCEPSS rescore
- 2026-08-16 14:55 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-09 22:58 UTCEG score recompute
- 2026-08-09 22:58 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 16:36 UTCEPSS rescore
- 2026-08-08 05:30 UTCEG score recompute
- 2026-08-08 05:30 UTCVendor advisory
- 2026-08-07 16:27 UTCEPSS rescore
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 07:20 UTCEG score recompute
- 2026-08-06 07:20 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 10:37 UTCEPSS rescore
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 11:49 UTCOSV refresh
- 2026-07-23 03:02 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 07:02 UTCOSV refresh
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-502
- CVE-2017-10992EG 9.8EPSS p96CRITICAL
- CVE-2013-4521EG 9.8EPSS p90CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS p98CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-10934EG 9.8CRITICAL
- CVE-2016-9498EG 9.8EPSS p97CRITICAL
- CVE-2016-9483EG 9.8CRITICAL
- CVE-2015-2020EG 9.8CRITICAL
- CVE-2017-15692EG 9.8EPSS p92CRITICAL
Frequently asked(5)
What is CVE-2025-68665?
When was CVE-2025-68665 disclosed?
Is CVE-2025-68665 actively exploited?
What is the CVSS score of CVE-2025-68665?
How do I remediate CVE-2025-68665?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68665
Is Your Infrastructure Affected by CVE-2025-68665?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.