Unsafe Deserialization in langchain-community (CVE-2024-5998)
Summary
Vulnerability in langchain-community (CVE-2024-5998). Confidential information can be exposed externally. Exploitable via FAISS.deserialize_from_bytes. Mitigation: upgrade to 0.2.4 or later.
Original description
The description as published by the source.
A vulnerability in the FAISS.deserialize_from_bytes function of langchain-ai/langchain allows for pickle deserialization of untrusted data. This can lead to the execution of arbitrary commands via the os.system function. The issue affects versions prior to 0.2.4.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-5998 has been found in langchain-community.
Attackers can target a specific entry point like FAISS.deserialize_from_bytes over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade langchain-community to 0.2.4 or later.
If unsure, ask your IT team or search "langchain-community CVE-2024-5998" on the vendor's site.
CVE-2024-5998 (langchain-community) — CWE-502
Attack vector: physical
Attack surface: FAISS.deserialize_from_bytes / os.system
Patched: 0.2.4 — 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.
Unsafe deserialization (CWE-502) exists in langchain-community. Attackers reach the vulnerable code path via FAISS.deserialize_from_bytes.
Check the vendor advisory for the affected versions of langchain-community. Attack surface: FAISS.deserialize_from_bytes / os.system.
Severity: ?. Confidential information can be exposed externally.
Update to 0.2.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'langchain-community' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'langchain-community' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
langchain-communityを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade langchain-community to 0.2.4ステージング環境で 0.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web huntr.com