# Crawlee for Python: SSRF via sitemap-derived URLs

Advisory record · `GHSA-3r75-xc34-5f44`

- **Identifiers:** `GHSA-3r75-xc34-5f44` · `CVE-2026-46497` · `PYSEC-2026-2430`
- **State:** Confirmed
- **Severity:** CVSS 2.3 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 21 May 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 May 2026, 19:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `crawlee` (PyPI): affected `>=1.0.0, <1.7.0`; fixed in `1.7.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Crawlee for Python versions 1.0.0 up to but not including 1.7.0 are vulnerable to server-side request forgery through sitemap and robots.txt content, where URLs pointing to internal hosts or non-HTTP schemes could be queued and fetched by the crawler. An attacker who controls a sitemap or robots.txt the crawler fetches can make it issue requests inside its network, which is mainly blind probing, and with CurlImpersonateHttpClient non-HTTP schemes such as gopher or file become reachable. Upgrade to crawlee 1.7.0, which is listed as the fixed version.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 2.3 Low, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0029, the 21st percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:02 UTC: First seen by agentprime
- 31 Oct 2026, 15:02 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3r75-xc34-5f44)

## Sources

- [GitHub Advisory Database: GHSA-3r75-xc34-5f44](https://github.com/advisories/GHSA-3r75-xc34-5f44)
- [OSV: GHSA-3r75-xc34-5f44](https://osv.dev/vulnerability/GHSA-3r75-xc34-5f44)
- <https://github.com/apify/crawlee-python/security/advisories/GHSA-3r75-xc34-5f44>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-46497>
- <https://github.com/apify/crawlee-python>
- <https://github.com/apify/crawlee-python/releases/tag/v1.7.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-3r75-xc34-5f44>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3r75-xc34-5f44/>. Everything for agents: <https://agentprime.io/llms.txt>.