SSRF (Server-Side Request Forgery) in crawlee (CVE-2026-46497)
Summary
SSRF in crawlee (CVE-2026-46497). Risk of unauthorized operations or information disclosure. Exploitable via Host header. Mitigation: upgrade to 1.7.0 or later.
Original description
The description as published by the source.
Crawlee is a web scraping and browser automation library. From version 1.0.0 to before version 1.7.0, Crawlee is vulnerable to SSRF via sitemap-derived URLs. This issue has been patched in version 1.7.0.
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-46497 has been found in crawlee.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade crawlee to 1.7.0 or later.
If unsure, ask your IT team or search "crawlee CVE-2026-46497" on the vendor's site.
CVE-2026-46497 (crawlee) — CWE-918
Attack surface: Host header / robots.txt / example.com / CurlImpersonateHttpClient
Patched: 1.7.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.
SSRF (CWE-918) exists in crawlee. Attackers reach the vulnerable code path via Host header.
Check the vendor advisory for the affected versions of crawlee. Attack surface: Host header / robots.txt / example.com / CurlImpersonateHttpClient.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.7.0.
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 'crawlee' . 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 'crawlee' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
crawleeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade crawlee to 1.7.0ステージング環境で 1.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- web github.com
- web github.com