Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.3amended

Scrapy's redirects ignoring scheme-specific proxy settings

GHSA-jm3v-qxmh-hxwv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (scrapy 2.11.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI scrapy

    Affected
    < 2.11.2
    Fixed in
    2.11.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact When using system proxy settings, which are scheme-specific (i.e. specific to http:// or https:// URLs), Scrapy was not accounting for scheme changes during redirects. For example, an HTTP request would use the proxy configured for HTTP and, when redirected to an HTTPS URL, the new HTTPS request would still use the proxy configured for HTTP instead of switching to the proxy configured for HTTPS. Same the other way around. If you have different proxy configurations for HTTP and HTTPS in your system for security reasons (e.g., maybe you don’t want one of your proxy providers to be aware of the URLs that you visit with the other one), this would be a security issue. Patches Upgrade to Scrapy 2.11.2. Workarounds Replace the built-in retry middlewares (RedirectMiddleware and MetaRefreshMiddleware) and the HttpProxyMiddleware middleware with custom ones that implement the fix from Scrapy 2.11.2, and verify that they work as intended. References This security issue was reported by…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-jm3v-qxmh-hxwv

  2. Revision 1 · created ·

    Published from osv record GHSA-jm3v-qxmh-hxwv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-jm3v-qxmh-hxwv

Advisory: Scrapy's redirects ignoring scheme-specific proxy settings
IDs: GHSA-jm3v-qxmh-hxwv
Record: https://patchnext.com/advisories/ghsa-jm3v-qxmh-hxwv (revision 2, source checked 26 Oct 2026, 13:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: scrapy 2.11.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI scrapy: affected < 2.11.2; fixed in 2.11.2

## Suggested inspection (read-only)
- `python -m pip show scrapy`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on scrapy.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jm3v-qxmh-hxwv (OSV record GHSA-jm3v-qxmh-hxwv lists affected ranges: PyPI scrapy >=0 <2.11.2 (fixed))
- Verified: https://github.com/advisories/GHSA-jm3v-qxmh-hxwv (GitHub-reviewed advisory GHSA-jm3v-qxmh-hxwv lists affected ranges: PyPI scrapy >=0 <2.11.2)

Commands are suggestions: review each one before running it.

Loading voting…