Technology · PyPI
scrapy (PyPI) vulnerabilities
Updated . Rebuilt every hour.
Junglewise Threat Intelligence has tracked 18 vulnerabilities in scrapy (PyPI): 0 in the last 7 days and 2 in the last 90 days, 0 of them critical and 0 exploited in the wild. The most recent, CVE-2026-105782, was published on 6 October 2026. Nothing in the last four weeks, down from 1 vulnerability in the four before.
- Last 7 days
- 0
- Last 90 days
- 2
- Critical, all time
- 0
- Exploited in the wild
- 0
About scrapy (PyPI)
Python web scraping framework for crawling websites and extracting structured data.
Latest scrapy (PyPI) vulnerabilities
- CVE-2026-105782: Scrapy arbitrary code execution via Referrer-Policy headerhighCVSS 7.5EPSS 0.4%
- CVE-2026-84366: Scrapy S3DownloadHandler cleartext transmission of AWS credentialshighCVSS 7.4EPSS 0.3%
- CVE-2025-6176: PYSEC-2026-2401 - Scrapy is vulnerable to a denial of service (DoS) attack due to flaws in brotli decompression…lowCVSS 3EPSS 0.5%
- CVE-2024-3572: PYSEC-2026-1907 - Scrapy decompression bomb vulnerabilitylowCVSS 3.1EPSS 0.8%
- CVE-2024-3574: PYSEC-2026-1908 - Scrapy authorization header leakage on cross-domain redirectlowCVSS 3.1EPSS 0.7%
- Duplicate Advisory: Scrapy leaks the authorization header on same-domain but cross-origin redirectslowCVSS 3
- CVE-2024-1968: PYSEC-2024-258 - In scrapy/scrapy, an issue was identified where the Authorization header is not removed during redirects…lowCVSS 3.1EPSS 0.7%
- Scrapy insecure redirect handling in non-HTTP protocolslowCVSS 3.1
- Scrapy's redirects ignoring scheme-specific proxy settingslowCVSS 3.1
- Duplicate Advisory: Scrapy decompression bomb vulnerabilitylowCVSS 3
- Duplicate Advisory: Scrapy authorization header leakage on cross-domain redirectlowCVSS 3
- Duplicate Advisory: ReDos vulnerability of XMLFeedSpiderlowCVSS 3
- CVE-2024-1892: Scrapy vulnerable to ReDoS via XMLFeedSpiderlowCVSS 3.1EPSS 0.6%
- Scrapy before 2.6.2 and 1.8.3 vulnerable to one proxy sending credentials to anotherinfo
- CVE-2017-14158: Scrapy uncontrolled resource consumption in S3FilesStorehighCVSS 7.5EPSS 2.6%
- Scrapy cookie-setting is not restricted based on the public suffix listinfo
- CVE-2022-0577: Scrapy cookie leakage across redirect domainsmediumCVSS 6.5EPSS 1.3%
- CVE-2021-41125: Scrapy HTTP authentication credentials potentially leaked to target websiteslowCVSS 3.1EPSS 1.3%
Most severe scrapy (PyPI) vulnerabilities
Exploited in the wild first, then by severity and CVSS score.
- CVE-2017-14158: Scrapy uncontrolled resource consumption in S3FilesStorehighCVSS 7.5EPSS 2.6%
- CVE-2026-105782: Scrapy arbitrary code execution via Referrer-Policy headerhighCVSS 7.5EPSS 0.4%
- CVE-2026-84366: Scrapy S3DownloadHandler cleartext transmission of AWS credentialshighCVSS 7.4EPSS 0.3%
- CVE-2022-0577: Scrapy cookie leakage across redirect domainsmediumCVSS 6.5EPSS 1.3%
- CVE-2021-41125: Scrapy HTTP authentication credentials potentially leaked to target websiteslowCVSS 3.1EPSS 1.3%
- CVE-2024-3572: PYSEC-2026-1907 - Scrapy decompression bomb vulnerabilitylowCVSS 3.1EPSS 0.8%
- CVE-2024-1968: PYSEC-2024-258 - In scrapy/scrapy, an issue was identified where the Authorization header is not removed during redirects…lowCVSS 3.1EPSS 0.7%
- CVE-2024-3574: PYSEC-2026-1908 - Scrapy authorization header leakage on cross-domain redirectlowCVSS 3.1EPSS 0.7%
- CVE-2024-1892: Scrapy vulnerable to ReDoS via XMLFeedSpiderlowCVSS 3.1EPSS 0.6%
- Scrapy insecure redirect handling in non-HTTP protocolslowCVSS 3.1
Vulnerabilities per week
Nothing in the last four weeks, down from 1 vulnerability in the four before. The last 13 weeks, by the week each vulnerability was published.
| Week of | Bar | Vulns | Critical |
|---|---|---|---|
| 17 Aug 2026 | 0 | 0 | |
| 24 Aug 2026 | 0 | 0 | |
| 31 Aug 2026 | 1 | 0 | |
| 7 Sep 2026 | 0 | 0 | |
| 14 Sep 2026 | 0 | 0 | |
| 21 Sep 2026 | 0 | 0 | |
| 28 Sep 2026 | 0 | 0 | |
| 5 Oct 2026 | 1 | 0 | |
| 12 Oct 2026 | 0 | 0 | |
| 19 Oct 2026 | 0 | 0 | |
| 26 Oct 2026 | 0 | 0 | |
| 2 Nov 2026 | 0 | 0 | |
| 9 Nov 2026 | 0 | 0 |
Embed a badge
A live badge for a README, a status page or an internal wiki: how many scrapy (PyPI) vulnerabilities were published in the last 7 days and how many of them are critical, refreshed hourly.
[](https://junglewise.ai/threats/technologies/scrapy)<a href="https://junglewise.ai/threats/technologies/scrapy"><img src="https://junglewise.ai/threats/technologies/scrapy/badge.svg" alt="scrapy (PyPI) vulnerabilities" /></a>How this is built
Junglewise Threat Intelligence collects vulnerabilities from NVD, GitHub Security Advisories, OSV, the CISA Known Exploited Vulnerabilities catalog, FIRST EPSS and vendor advisories, and matches each one to the technologies and vendors it affects. Dates are the date a vulnerability was published, in UTC.
The pages are rebuilt from the database every hour. Frozen weekly and monthly reports never change once published, so they can be cited.
Use this data
The same data is at https://junglewise.ai/threats/technologies/scrapy.json, and this page as text at https://junglewise.ai/threats/technologies/scrapy.md, for scripts and language models. It is free to reuse under CC BY 4.0 with a link back to this page.
Cite as: Junglewise Threat Intelligence, "scrapy (PyPI) vulnerabilities", https://junglewise.ai/threats/technologies/scrapy, 13 November 2026.