Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2025-68664

Unsafe Deserialization in langchain-core (CVE-2025-68664)

Summary

vulnerability in langchain-core (CVE-2025-68664). Confidential information can be exposed externally. Exploitable via ``metadata``. Mitigation: upgrade to `0.3.81, 1.2.5` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2025-68664** has been found in langchain-core. Attackers can target a specific entry point like ``metadata`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade langchain-core to **0.3.81, 1.2.5** or later. If unsure, ask your IT team or search "langchain-core CVE-2025-68664" on the vendor's site.
CVE-2025-68664 (langchain-core) — CWE-502 / Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `metadata` / `additional_kwargs` / `response_metadata` / `Serializable` Patched: `0.3.81, 1.2.5` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**unsafe deserialization** (CWE-502) exists in langchain-core. Attackers reach the vulnerable code path via ``metadata`` without authentication.
📍 Affected scope
langchain-core — . Attack surface: `metadata` / `additional_kwargs` / `response_metadata` / `Serializable`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **0.3.81, 1.2.5**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'langchain-core' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'langchain-core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `langchain-core` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade langchain-core to 0.3.81, 1.2.5

    ステージング環境で 0.3.81, 1.2.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI langchain-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.81"},{"introduced":"1.0.0"},{"fixed":"1.2.5"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →