← Back
CVE-2023-36095
critical
CVSS 9.8
Code Injection in langchain (CVE-2023-36095)
Summary
code injection in langchain (CVE-2023-36095). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `0.0.236` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2023-36095** has been found in langchain.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade langchain to **0.0.236** or later.
If unsure, ask your IT team or search "langchain CVE-2023-36095" on the vendor's site.
CVE-2023-36095 (langchain) — CWE-94 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `0.0.236` — 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
**arbitrary code execution** (CWE-94) exists in langchain.
📍 Affected scope
langchain — .
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.0.236**.
🛡️ 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' .` 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
-
1Identify exposure identify
grep -r 'langchain' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `langchain` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade langchain to 0.0.236ステージング環境で 0.0.236 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
langchain
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.236"}]}]