CVE-2026-46497 json
SSRF via sitemap-derived URLs in Crawlee for Python
published 5mo ago modified 14d ago also GHSA-3r75-xc34-5f44 , PYSEC-2026-2430 , EUVD-2026-36067
- cvss
- 2.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2026-46497 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N |
| CNA | 4.0 | 2.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | crawlee | >=1.0.0, <1.7.0 |
1.7.0 |
Affected products
- apify crawlee-python
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/apify/crawlee-python/security/advisories/GHSA-3r75-xc34-5f44
web
-
github.com
/apify/crawlee-python/releases/tag/v1.7.0
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-46497
advisory
-
github.com
/apify/crawlee-python
package
-
pypi.org
/project/crawlee
package
-
github.com
/advisories/GHSA-3r75-xc34-5f44
advisory
Sources
- CVE List CVE-2026-46497
- GitHub Advisory GHSA-3r75-xc34-5f44
- NVD CVE-2026-46497
- OSV PYSEC-2026-2430
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.