← Back
CVE-2025-67743
SSRF (Server-Side Request Forgery) in local-deep-research (CVE-2025-67743)
Summary
SSRF in local-deep-research (CVE-2025-67743). Confidential information can be exposed externally. Exploitable via `POST /api/resources/`. Mitigation: upgrade to `1.3.9` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-67743** has been found in local-deep-research.
Attackers can target a specific entry point like `POST /api/resources/` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade local-deep-research to **1.3.9** or later.
If unsure, ask your IT team or search "local-deep-research CVE-2025-67743" on the vendor's site.
CVE-2025-67743 (local-deep-research) — CWE-918 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/resources/ / `download_service.py` / `safe_requests.py` / `internal_service.py`
Patched: `1.3.9` — 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
**SSRF** (CWE-918) exists in local-deep-research. Attackers reach the vulnerable code path via `POST /api/resources/` without authentication.
📍 Affected scope
local-deep-research — . Attack surface: POST /api/resources/ / `download_service.py` / `safe_requests.py` / `internal_service.py`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.3.9**.
🛡️ 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 `POST /api/resources/` requests with malformed payloads or SQL meta-characters. Run `grep -r 'local-deep-research' .` 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 'local-deep-research' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `local-deep-research` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/resources/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/resources/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade local-deep-research to 1.3.9ステージング環境で 1.3.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /api/resources/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
local-deep-research
[{"type":"ECOSYSTEM","events":[{"introduced":"1.3.0"},{"fixed":"1.3.9"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-67743
- advisory https://github.com/advisories/GHSA-9c54-gxh7-ppjc
- package https://github.com/LearningCircuit/local-deep-research
- package https://pypi.org/project/local-deep-research
- web https://github.com/LearningCircuit/local-deep-research/security/advisories/GHSA-9c54-gxh7-ppjc
- web https://github.com/LearningCircuit/local-deep-research/commit/b79089ff30c5d9ae77e6b903c408e1c26ad5c055