Vulnerability in langchain-exa (CVE-2024-58340)
Summary
Vulnerability in langchain-exa (CVE-2024-58340). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.0.0a1 or later.
Original description
The description as published by the source.
LangChain versions up to and including 0.3.1 contain a regular expression denial-of-service (ReDoS) vulnerability in the MRKLOutputParser.parse() method (libs/langchain/langchain/agents/mrkl/output_parser.py). The parser applies a backtracking-prone regular expression when extracting tool actions from model output. An attacker who can supply or influence the parsed text (for example via prompt injection in downstream applications that pass LLM output directly into MRKLOutputParser.parse()) can trigger excessive CPU consumption by providing a crafted payload, causing significant parsing delays and a denial-of-service condition.
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-58340 has been found in langchain-exa.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade langchain-exa to 1.0.0a1 or later.
If unsure, ask your IT team or search "langchain-exa CVE-2024-58340" on the vendor's site.
CVE-2024-58340 (langchain-exa) — CWE-1333 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.0.0a1 — 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.
A vulnerability (CWE-1333) exists in langchain-exa.
Check the vendor advisory for the affected versions of langchain-exa.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.0.0a1.
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-exa' . 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-exa' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
langchain-exaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade langchain-exa to 1.0.0a1ステージング環境で 1.0.0a1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory disclosure@vulncheck.com
- exploit disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com