← Back
CVE-2026-40087

Vulnerability in langchain-core (CVE-2026-40087)

Summary

vulnerability in langchain-core (CVE-2026-40087). Risk of unauthorized operations or information disclosure. Exploitable via ``PromptTemplate``. Mitigation: upgrade to `1.2.28` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-40087** has been found in langchain-core. Attackers can target a specific entry point like ``PromptTemplate`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade langchain-core to **1.2.28** or later. If unsure, ask your IT team or search "langchain-core CVE-2026-40087" on the vendor's site.
CVE-2026-40087 (langchain-core) — CWE-1336 / Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `PromptTemplate` / `DictPromptTemplate` / `ImagePromptTemplate` Patched: `1.2.28` — 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
**A vulnerability** (CWE-1336) exists in langchain-core. Attackers reach the vulnerable code path via ``PromptTemplate`` without authentication.
📍 Affected scope
langchain-core — . Attack surface: `PromptTemplate` / `DictPromptTemplate` / `ImagePromptTemplate`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.2.28**.
🛡️ 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 1.2.28

    ステージング環境で 1.2.28 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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":"1.0.0a1"},{"fixed":"1.2.28"}]}]

References

🍪 About cookies

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

Details →