Scrapy's redirects ignoring scheme-specific proxy settings
Affects scrapySource GCVE Database
CVSS 4.3 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:L/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 issue is fixed. Alternatively, implement custom middleware replacements for RedirectMiddleware, MetaRefreshMiddleware, and HttpProxyMiddleware that incorporate the fix from Scrapy 2.11.2. Verify the custom solution correctly handles scheme-specific proxy switching during redirects.
Description
Scrapy versions from 2.9.0 up to but not including 2.11.2 have a vulnerability where redirects do not properly switch proxy settings based on URL scheme changes (HTTP to HTTPS or vice versa). This causes the proxy configured for one scheme to be incorrectly used for the other, potentially leaking browsing information between proxies. The issue is fixed in Scrapy 2.11.2.