scrapy
Affected
- introduced
1.4.0, fixed2.14.2(ecosystem)
Fixed versions
2.14.2
Fix
- Fixed version
2.14.2pip install --upgrade scrapy==2.14.2
Advisory
Also known as: CVE-2026-105782, PYSEC-2026-4299
Scrapy: Arbitrary Module Import via Referrer-Policy Header in RefererMiddleware
Impact
Since version 1.4.0, Scrapy respects the Referrer-Policy response header to decide whether and how to set a Referer header on follow-up requests.
If the header value looked like a valid Python import path, Scrapy would import the referenced object and call it, assuming it referred to a referrer policy class (for example, scrapy.spidermiddlewares.referer.DefaultReferrerPolicy) and attempting to instantiate it to handle the Referer header.
A malicious site could exploit this by setting Referrer-Policy to a path such as sys.exit, causing Scrapy to import and execute it and potentially terminate the process.
Patches
Upgrade to Scrapy 2.14.2 (or later).
Workarounds
If you cannot upgrade to Scrapy 2.14.2, consider the following mitigations.
Referer header on follow-up requests, set `REFERER_ENABLED` to False.Referer, disable the middleware and set the header explicitly on the requests that require it.Referrer-Policy. For example:Request(
url,
meta={
"referrer_policy": "scrapy.spidermiddlewares.referer.DefaultReferrerPolicy",
},
)
Instead of editing requests individually, you can:
referrer_policy meta key; orIf you want to continue respecting legitimate Referrer-Policy headers while protecting against malicious ones, disable the built-in referrer policy middleware by setting it to None in `SPIDER_MIDDLEWARES` and replace it with the fixed implementation from Scrapy 2.14.2.
If the Scrapy 2.14.2 implementation is incompatible with your project (for example, because your Scrapy version is older), copy the corresponding middleware from your Scrapy version, apply the same patch, and use that as a replacement.
High Basis: The source's own band: HIGH
1.4.0, fixed 2.14.2 (ecosystem)2.14.2
2.14.2pip install --upgrade scrapy==2.14.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0