GHSA-9X8M-2XPF-CRP3

Scrapy before 2.6.2 and 1.8.3 vulnerable to one proxy sending credentials to another

Workarounds

If you cannot upgrade, make sure that any code that changes the value of the proxy request meta also removes the Proxy-Authorization header from the request if present.

For more information

If you have any questions or comments about this advisory:

• Open an issue
• Email us

When the built-in HTTP proxy downloader middleware processes a request with proxy metadata, and that proxy metadata includes proxy credentials, the built-in HTTP proxy downloader middleware sets the Proxy-Authentication header, but only if that header is not already set.

There are third-party proxy-rotation downloader middlewares that set different proxy metadata every time they process a request.

Because of request retries and redirects, the same request can be processed by downloader middlewares more than once, including both the built-in HTTP proxy downloader middleware and any third-party proxy-rotation downloader middleware.

These third-party proxy-rotation downloader middlewares could change the proxy metadata of a request to a new value, but fail to remove the Proxy-Authentication header from the previous value of the proxy metadata, causing the credentials of one proxy to be leaked to a different proxy.

If you rotate proxies from different proxy providers, and any of those proxies requires credentials, you are affected, unless you are handling proxy rotation as described under Workarounds below. If you use a third-party downloader middleware for proxy rotation, the same applies to that downloader middleware, and installing a patched version of Scrapy may not be enough; patching that downloader middlware may be necessary as well.

Kodem intelligence

Already deployed Kodem?

Upgrade to Scrapy 2.6.2.

If you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.6.2 is not an option, you may upgrade to Scrapy 1.8.3 instead.

1. What is GHSA-9X8M-2XPF-CRP3? GHSA-9X8M-2XPF-CRP3 is a medium-severity security vulnerability in scrapy (pip), affecting versions < 1.8.3. It is fixed in 1.8.3, 2.6.2.
2. Which versions of scrapy are affected by GHSA-9X8M-2XPF-CRP3? scrapy (pip) versions < 1.8.3 is affected.
3. Is there a fix for GHSA-9X8M-2XPF-CRP3? Yes. GHSA-9X8M-2XPF-CRP3 is fixed in 1.8.3, 2.6.2. Upgrade to this version or later.
4. Is GHSA-9X8M-2XPF-CRP3 exploitable, and should I be worried? Whether GHSA-9X8M-2XPF-CRP3 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether GHSA-9X8M-2XPF-CRP3 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix GHSA-9X8M-2XPF-CRP3?
   • Upgrade scrapy to 1.8.3 or later
   • Upgrade scrapy to 2.6.2 or later

Other vulnerabilities in scrapy