Advisory record · GHSA-4qqq-9vqf-3h3f

In scrapy/scrapy, an issue was identified where the Authorization header is not removed during redirects that only change the scheme (e.g., HTTPS to HTTP) but remain within the same domain. This be...

CVSS 7.5 HighEPSS 0.0069 · 53rd percentile

Published by the GitHub Advisory Database at 20 May 2024, 08:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
scrapyPyPI<1d0502f25bbe55a22899af915623fda1aaeb9dd8 || <2.0.0 || >=2.0.0, <2.11.21d0502f25bbe55a22899af915623fda1aaeb9dd8, 2.0.0, 2.11.2
Identifiers
GHSA-4qqq-9vqf-3h3f · CVE-2024-1968 · PYSEC-2024-258
Weakness (CWE)
CWE-200
Published
20 May 2024
Updated
10 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Scrapy versions before 2.11.2 (including the 2.0.0 range listed as affected) do not remove the Authorization header when a redirect changes only the scheme, such as HTTPS to HTTP, on the same domain. An attacker who can intercept or sit on the network path of a downgraded request could read the header in plaintext and obtain credentials. Upgrade to Scrapy 2.11.2 or later. The source gives few details on the exact affected version range.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.0069, the 53rd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 20 May 2024. New records show when each source confirmed them.

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.