CVE-2025-6176: scrapy/scrapy · Uncontrolled Resource Consumption
Affects scrapy/scrapySource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 31 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIscrapypkg:pypi/scrapyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Immediate mitigation steps include monitoring and restricting brotli compressed content from untrusted sources within Scrapy workflows. Organizations should consider disabling brotli decompression temporarily if possible or implementing custom decompression limits to prevent excessive memory usage. Deploying resource usage monitoring and alerting on memory spikes during scraping operations can help detect exploitation attempts early. Once patches are released by the Scrapy project, prompt updating to a fixed version is critical. Additionally, network-level controls such as web proxies or firewalls can be configured to filter or limit brotli compressed responses from suspicious or untrusted endpoints. For critical environments, isolating scraping workloads in containers or sandboxes with strict memory limits can reduce the risk of system-wide impact. Finally, reviewing and hardening the overall scraping infrastructure to handle unexpected resource consumption will improve resilience against similar future threats.
Description
Scrapy versions up to 2.13.2 are vulnerable to a denial of service (DoS) attack due to a flaw in its brotli decompression implementation. The protection mechanism against decompression bombs fails to mitigate the brotli variant, allowing remote servers to crash clients with less than 80GB of available memory. This occurs because brotli can achieve extremely high compression ratios for zero-filled data, leading to excessive memory consumption during decompression.