CVE-2021-41125Medium· 5.7▾ SunlitScrapy HTTP authentication credentials potentially leaked to target websites
▾ Sunlit zone — Low / medium · no exploitation signal
impact 31.4 · likelihood 0.3 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
1.2%
1.2% → 1.3%
If you use HttpAuthMiddleware (i.e. the http_user and http_pass spider attributes) for HTTP authentication, all requests will expose your credentials to the request target.
This includes requests generated by Scrapy components, such as robots.txt requests sent by Scrapy when the ROBOTSTXT_OBEY setting is set to True, or as requests reached through redirects.
Upgrade to Scrapy 2.5.1 and use the new http_auth_domain spider attribute to control which domains are allowed to receive the configured HTTP authentication credentials.
If you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.5.1 is not an option, you may upgrade to Scrapy 1.8.1 instead.
If you cannot upgrade, set your HTTP authentication credentials on a per-request basis, using for example the w3lib.http.basic_auth_header function to convert your credentials into a value that you can assign to the Authorization header of your request, instead of defining your credentials globally using HttpAuthMiddleware.
If you have any questions or comments about this advisory:
scrapy < 1.8.1scrapy >= 2.0.0, < 2.5.1Upgrade to a patched release:
scrapy 1.8.1scrapy 2.5.1Connected by shared product, vendor, weakness, or advisory.
CVE-2026-84366High· 7.4Scrapy is a high-level web crawling and scraping framework for Python
CVE-2024-3574High· 7.5Scrapy authorization header leakage on cross-domain redirect
CVE-2024-3572High· 7.5Scrapy decompression bomb vulnerability