NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

CVE-2024-3572: Scrapy decompression bomb vulnerability

highCVSS 3.1 7.5GHSA-7j7m-v7m3-jqm7

Impact Scrapy limits allowed response sizes by default through the DOWNLOADMAXSIZE and DOWNLOADWARNSIZE settings. However, those limits were only being enforced during the download of the raw, usually-compressed response bodies, and not during decompression, making Scrapy vulnerable to decompression bombs.

Published Feb 16, 2024 · Updated Mar 22, 2026

Affected packages

scrapy

Ecosystem
PyPI
Affected
>= 2.0.0, < 2.11.1
Fixed in
2.11.1
Check
pip show scrapy

scrapy

Ecosystem
PyPI
Affected
< 1.8.4
Fixed in
1.8.4
Check
pip show scrapy

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

Scrapy limits allowed response sizes by default through the `DOWNLOAD_MAXSIZE` and `DOWNLOAD_WARNSIZE` settings.

However, those limits were only being enforced during the download of the raw, usually-compressed response bodies, and not during decompression, making Scrapy vulnerable to decompression bombs.

A malicious website being scraped could send a small response that, on decompression, could exhaust the memory available to the Scrapy process, potentially affecting any other process sharing that memory, and affecting disk usage in case of uncompressed response caching.

Patches

Upgrade to Scrapy 2.11.1.

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

Workarounds

There is no easy workaround.

Disabling HTTP decompression altogether is impractical, as HTTP compression is a rather common practice.

However, it is technically possible to manually backport the 2.11.1 or 1.8.4 fix, replacing the corresponding components of an unpatched version of Scrapy with patched versions copied into your own code.

Acknowledgements

This security issue was reported by @dmandefy through huntr.com.

Credited to dmandefy.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More PyPI vulnerabilities

All PyPI entries