Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ GHSA-cwxj-rr6w-m6w7 — scrapy

🟠 CVSS 8.0 — High ✅ No Known Exploit CWE-470 OSV
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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.

  • Disable the middleware: If you don't need the Referer header on follow-up requests, set [REFERER_ENABLED](https://docs.scrapy.org/en/latest/topics/spider-middleware.html#referer-enabled) to False.
  • Set headers manually: If you do need a Referer, disable the middleware and set the header explicitly on the requests that require it.
  • Set referrer_policy in request metadata: If disabling the middleware is not viable, set the [referrer_policy](https://docs.scrapy.org/en/latest/topics/spider-middleware.html#referrer-policy) request meta key on all requests to prevent evaluating preceding responses' Referrer-Policy. For example:

```python

Request(

url,

meta={

"referrer_policy": "scrapy.spidermiddlewares.referer.DefaultReferrerPolicy",

},

)

```

Instead of editing requests individually, you can:

  • implement a custom [spider middleware](https://docs.scrapy.org/en/latest/topics/spider-middleware.html) that runs before the built-in referrer policy middleware and sets the referrer_policy meta key; or
  • set the meta key in start requests and use the [scrapy-sticky-meta-params](https://github.com/heylouiz/scrapy-sticky-meta-params) plugin to propagate it to follow-up requests.

If 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](https://docs.scrapy.org/en/latest/topics/settings.html#std-setting-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.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Weakness class

GHSA-cwxj-rr6w-m6w7 is classified as CWE-470: Unsafe Reflection. Input selects which class or method to invoke, letting an attacker reach code that was never meant to be callable.

Affected software

GHSA-cwxj-rr6w-m6w7 is recorded against 1 package.

  • scrapy (from 1.4.0 up to 2.14.2)

Timeline and source

Published on 13 March 2026 and last revised on 14 March 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

github.com (Web)
github.com (Web)
github.com (Package)

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE CWE-470
Public Exploit ✅ No
Source OSV
Published 2026-03-13
Updated 2026-08-20
Modified 2026-03-14
Fix URL N/A

Affected Packages

Software From version Fixed in
scrapy 1.4.0 2.14.2

Similar Threats

Site Security Check

Is scrapy part of your stack?

GHSA-cwxj-rr6w-m6w7 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.