SSRF (Server-Side Request Forgery) in local-deep-research (CVE-2026-46526)
Summary
SSRF in local-deep-research (CVE-2026-46526). Risk of unauthorized operations or information disclosure. Exploitable via validate_url. Mitigation: upgrade to 1.6.10 or later.
Original description
The description as published by the source.
Local Deep Research is an AI-powered research assistant for deep, iterative research. Prior to 1.6.10, the URL checking logic in local-deep-research has a logical flaw that could be bypassed by attackers, leading to SSRF attacks. The current project uses validate_url to validate the input URL. The main logic is to perform security checks on the host portion of the URL extracted by urlparse to prevent SSRF attacks. However, there are indeed differences in parsing between urlparse and the library that actually sends the request. For example, in safe_get, validate_url is first used to perform an SSRF check, and then requests.get is used to send the actual request. This vulnerability is fixed in 1.6.10.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
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-2026-46526 has been found in local-deep-research.
Attackers can target a specific entry point like validate_url over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/10.
What to do: upgrade local-deep-research to 1.6.10 or later.
If unsure, ask your IT team or search "local-deep-research CVE-2026-46526" on the vendor's site.
CVE-2026-46526 (local-deep-research) — CWE-918 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: validate_url / safe_get / requests.get / main
Patched: 1.6.10 — 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.
SSRF (CWE-918) exists in local-deep-research. Attackers reach the vulnerable code path via validate_url.
Check the vendor advisory for the affected versions of local-deep-research. Attack surface: validate_url / safe_get / requests.get / main.
Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure.
Update to 1.6.10.
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 'local-deep-research' . 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 'local-deep-research' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
local-deep-researchを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade local-deep-research to 1.6.10ステージング環境で 1.6.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com