Scrapy Allows Redirect Following
Affects scrapySource GCVE Database
CVSS 6.5 Medium : upgrade to 2.11.2 when convenient.
Data as of 18 Sep 2026, 01:50 UTC
- Patch
- Available – fixed in 2.11.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NWhat to do
Upgrade scrapy to 2.11.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewscrapypkg:brew/scrapyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Scrapy to version 2.11.2 or later, where this redirect handling issue is fixed. Alternatively, replace the built-in RedirectMiddleware and MetaRefreshMiddleware with custom implementations that restrict redirects to HTTP and HTTPS schemes as per the fix in 2.11.2. Verify that custom middleware correctly enforces these restrictions.
Description
Scrapy versions from 2.9.0 up to but not including 2.11.2 improperly followed redirects for URL schemes beyond HTTP and HTTPS, such as file://, ftp://, and s3://. This behavior could allow an attacker with the ability to control start requests and read spider output to access local files or sensitive credentials via redirected URLs. The vulnerability is fixed in Scrapy 2.11.2.