CVE-2024-1968: In scrapy/scrapy, an issue was identified where the Authorization header is not removed during redirects that

This week

HIGH 7.5REMOTEUPGRADE

CVE-2024-1968 is a high-severity flaw (CVSS 7.5) affecting scrapy. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 behavior contravenes the Fetch standard, which mandates the removal of Authorization headers in cross-origin requests when the scheme, host, or port changes. Consequently, when a redirect downgrades from HTTPS to HTTP, the Authorization header may be inad

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-200
Published	2024-05-20
Last modified	2026-06-17

Publisher (CNA): huntr.dev · Vendor: scrapy

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-05-20 08:15 UTCPublished CVE record published
2026-06-17 07:05 UTCUpdated Record last modified

scrapy scrapy UPGRADE

Affected: <= 1.8.4 · >= 2.0.0 and < 2.11.2

Fixed in: 2.11.2

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy scrapy || rpm -q scrapy || scrapy --version

2. UPGRADE to 2.11.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade scrapy

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade scrapy

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison scrapy sudo apt install scrapy=<VERSION_BEFORE_2.0.0> sudo apt-mark hold scrapy

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list scrapy sudo dnf downgrade scrapy-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add scrapy

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-1968?

scrapy: upgrade to 2.11.2. Exact commands for each OS are on this page.

Is CVE-2024-1968 being exploited?

CVE-2024-1968 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-1968 affect?

CVE-2024-1968 affects scrapy. Severity is high (CVSS 7.5). 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 behavior contravenes the Fetch standard, whic

How urgent is CVE-2024-1968?

Priority 49/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2024-3574 HIGH 7.5 UPGRADE In scrapy version 2.10.1, an issue was identified where the Authorization header, containing credentials for s
CVE-2024-3572 HIGH 7.5 UPGRADE The scrapy/scrapy project is vulnerable to XML External Entity (XXE) attacks due to the use of lxml.etree.from
CVE-2024-1892 MEDIUM 6.5 UPGRADE A Regular Expression Denial of Service (ReDoS) vulnerability exists in the XMLFeedSpider class of the scrapy/s

References

← Back to latest CVEs