Overview
The CVE-2025-48989 represents a critical vulnerability in Apache Tomcat, which allows attackers to exploit an improper resource shutdown or release. This vulnerability significantly impacts a wide range of Apache Tomcat versions, making them susceptible to a ‘made you reset’ attack. Due to the widespread use of Apache Tomcat, this vulnerability is of significant concern as it could potentially lead to system compromise or data leakage.
Vulnerability Summary
CVE ID: CVE-2025-48989
Severity: High (CVSS: 7.5)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise or data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
Apache Tomcat | 11.0.0-M1 through 11.0.9
Apache Tomcat | 10.1.0-M1 through 10.1.43
Apache Tomcat | 9.0.0.M1 through 9.0.107
How the Exploit Works
The vulnerability stems from an improper resource shutdown or release within Apache Tomcat. This flaw can be exploited by an attacker to trigger a ‘made you reset’ attack. The attacker sends maliciously crafted packets to the server, causing improper handling of resources. This can lead to unexpected system behavior, potentially compromising the system or leading to data leakage.
Conceptual Example Code
An example of how this vulnerability might be exploited could look something like the following HTTP request:
POST /vulnerable/resource HTTP/1.1
Host: target.example.com
Content-Type: application/x-www-form-urlencoded
payload=<malicious_payload>
In this example, `
