CVE-2025-48988VulnerabilityPublished 16 Jun 2025Updated 3 Nov 2025

CVE-2025-48988: Apache Tomcat · Unthrottled Resource Allocation

Affects Apache TomcatSource CVE Database V5

Not known to be exploited · 30% EPSS · CVSS 7.5 High · fixed in 11.0.8 : patch Apache Tomcat soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 30.4% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 11.0.8, 10.1.42, 9.0.106 +1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade org.apache.tomcat/tomcat to 11.0.8, 10.1.42, 9.0.106 or 8.5.101.

Affected software

Product	Affected	Fixed in
Mavenorg.apache.tomcat/tomcat`pkg:maven/org.apache.tomcat/tomcat`Other threats	Affected =11.0.0-M1 <11.0.8 =10.1.0-M1 <10.1.42 =9.0.0-M1 <9.0.106 =8.5.0 <8.5.101	Fixed in 11.0.8 10.1.42 9.0.106 8.5.101

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately upgrade Apache Tomcat to the fixed versions: 11.0.8, 10.1.42, or 9.0.106. 2. Implement resource usage monitoring and alerting on Tomcat servers to detect abnormal spikes in CPU, memory, or thread consumption. 3. Configure network-level protections such as rate limiting, web application firewalls (WAFs), and intrusion prevention systems (IPS) to limit the volume of requests to Tomcat services. 4. Review and tighten Tomcat connector and thread pool configurations to impose sensible limits on concurrent connections and resource allocation. 5. Conduct regular vulnerability scans and penetration tests focusing on resource exhaustion vectors. 6. For legacy or EOL Tomcat versions that cannot be immediately upgraded, consider isolating them behind reverse proxies or load balancers with strict traffic controls. 7. Maintain an incident response plan to quickly address potential denial of service incidents.

Description

Allocation of Resources Without Limits or Throttling vulnerability in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.7, from 10.1.0-M1 through 10.1.41, from 9.0.0.M1 through 9.0.105. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.8, 10.1.42 or 9.0.106, which fix the issue.

Impact

For European organizations, the primary impact is denial of service leading to downtime of web applications and services hosted on vulnerable Apache Tomcat servers. This can disrupt business operations, degrade customer experience, and potentially cause financial losses. Public sector entities, financial institutions, and large enterprises that rely heavily on Java-based web infrastructure are particularly vulnerable. The lack of authentication or user interaction required for exploitation increases the risk of automated attacks. Additionally, prolonged service outages could affect compliance with service-level agreements and regulatory requirements. The vulnerability could also be leveraged as part of a multi-stage attack to distract or exhaust defenses while other malicious activities occur. Organizations with limited patch management capabilities or legacy systems are at higher risk.

Summary

CVE-2025-48988 is a resource allocation vulnerability classified under CWE-770, affecting Apache Tomcat versions from 8.5.0 through 11.0.7, including some end-of-life versions. The flaw arises because Tomcat does not impose sufficient limits or throttling on resource allocation, allowing an attacker to consume excessive server resources such as memory, CPU, or threads. This can be triggered remotely without authentication or user interaction, making it a network-exploitable denial of service vector. The vulnerability impacts the availability of Tomcat servers by potentially causing crashes or severe performance degradation. Apache has addressed this issue in versions 11.0.8, 10.1.42, and 9.0.106 by introducing proper resource management and throttling mechanisms. Although no exploits have been observed in the wild yet, the vulnerability’s characteristics and CVSS score of 7.5 indicate a significant risk, especially for internet-facing Tomcat deployments. Organizations relying on Tomcat for critical web applications should prioritize upgrading and monitoring resource consumption to prevent exploitation.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2025, 01:45 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats