← Back
CVE-2026-45134
Unsafe Deserialization in langsmith (CVE-2026-45134)
Summary
vulnerability in langsmith (CVE-2026-45134). Risk of unauthorized operations or information disclosure. Exploitable via ``pull_prompt``. Mitigation: upgrade to `0.8.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45134** has been found in langsmith.
Attackers can target a specific entry point like ``pull_prompt`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade langsmith to **0.8.0** or later.
If unsure, ask your IT team or search "langsmith CVE-2026-45134" on the vendor's site.
CVE-2026-45134 (langsmith) — CWE-502 /
Attack surface: `pull_prompt` / `pull_prompt_commit` / `pullPrompt` / `pullPromptCommit`
Patched: `0.8.0` — 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 langsmith. Attackers reach the vulnerable code path via ``pull_prompt`` without authentication.
📍 Affected scope
langsmith — . Attack surface: `pull_prompt` / `pull_prompt_commit` / `pullPrompt` / `pullPromptCommit`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.8.0**.
🛡️ 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 'langsmith' .` 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 'langsmith' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `langsmith` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade langsmith to 0.8.0ステージング環境で 0.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
langsmith
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.8.0"}]}]
npm
langsmith
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.6.0"}]}]
pip
langchain-classic
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.7"}]}]
pip
langchain
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.30"}]}]