CVE-2025-49007: rack · Unthrottled Resource Allocation
Affects rackSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 6.6 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 4 Jun 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 |
|---|---|---|
RubyGemsrackpkg:gem/rackOther 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
European organizations should prioritize upgrading Rack to version 3.1.16 or later, where the vulnerability is patched. For organizations unable to immediately upgrade, implementing web application firewalls (WAFs) with rules to detect and block suspicious or malformed Content-Disposition headers in multipart requests can provide temporary protection. Rate limiting and request throttling on endpoints handling multipart form data can reduce the risk of resource exhaustion. Monitoring application logs for abnormal request patterns or spikes in CPU usage related to multipart parsing can help detect exploitation attempts early. Developers should review multipart parsing logic to ensure proper input validation and resource management. Additionally, organizations should maintain an inventory of applications using Rack and Ruby on Rails to assess exposure and prioritize remediation. Coordinating with incident response teams to prepare for potential denial of service incidents and establishing communication plans for affected users is also recommended.
Description
Rack is a modular Ruby web server interface. Starting in version 3.1.0 and prior to version 3.1.16, there is a denial of service vulnerability in the Content-Disposition parsing component of Rack. This is very similar to the previous security issue CVE-2022-44571. Carefully crafted input can cause Content-Disposition header parsing in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. This header is used typically used in multipart parsing. Any applications that parse multipart posts using Rack (virtually all Rails applications) are impacted. Version 3.1.16 contains a patch for the vulnerability.