dbcve.org
TomcatWeb server / proxy · Apache

CVE-2025-48989

HIGH · 7.5 CVSS v3.1 Published 2025-08-13
Fix available
A fix is available. Upgrade to 9.0.108 / 10.1.44 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Resource Shutdown or Release vulnerability in Apache Tomcat made Tomcat vulnerable to the made you reset attack. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.9, from 10.1.0-M1 through 10.1.43 and from 9.0.0.M1 through 9.0.107. Older, EOL versions may also be affected. Users are recommended to upgrade to one of versions 11.0.10, 10.1.44 or 9.0.108 which fix the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Tomcat contains an improper resource shutdown or release vulnerability that makes it susceptible to a 'made you reset' attack. This appears to be a connection handling issue where resources are not properly cleaned up, potentially allowing an attacker to reset connections or cause resource exhaustion.

MitigationUpgrade Apache Tomcat to version 11.0.10, 10.1.44, or 9.0.108 (depending on your major version) to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TomcatWeb server / proxy
Affected:>= 9.0.1, < 9.0.108>= 10.0.0, < 10.1.44>= 11.0.0, < 11.0.10= 9.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Tomcat installation
    Locate the Tomcat installation directory and verify it is Apache Tomcat (not another servlet container). Check for the presence of bin/catalina.sh or bin/catalina.bat, and the conf/server.xml configuration file.
    Affected if The installation is Apache Tomcat and matches the product listed in this CVE.
  2. Determine installed Tomcat version
    Run the version command from the Tomcat bin directory: on Linux/Unix run './version.sh', on Windows run 'version.bat'. This outputs the server version information including the Apache Tomcat version number.
    Affected if The version output shows a version within the affected ranges: 9.0.0, or 9.0.1 through 9.0.107; 10.0.0 through 10.1.43; 11.0.0 through 11.0.9.
  3. Confirm version from release artifacts
    If the bin scripts are not readily executable, check for a VERSION file in the root Tomcat directory, or inspect the MANIFEST.MF file within the lib/catalina.jar archive for the Implementation-Version attribute.
    Affected if The version read from these files matches one of the affected version ranges listed in this CVE.
  4. Verify network-exposed connector configuration
    Review the conf/server.xml file and identify any <Connector> elements defined with network-facing attributes such as 'port' and 'protocol' (for example, HTTP connectors on port 8080 or 80). The vulnerability affects connection handling, so an exposed network listener is required for exploitation.
    Affected if Tomcat has an active network connector configured that accepts remote connections, making the connection handling vulnerable to the resource cleanup issue.

You are affected if the installed Apache Tomcat version matches any of the following: 9.0.0, 9.0.1-9.0.107, 10.0.0-10.1.43, or 11.0.0-11.0.9, and the server has a network-exposed connector configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.108 / 10.1.44 / 11.0.10 or later
Fixed in 9.0.10810.1.4411.0.10
Interim mitigation

Upgrade Apache Tomcat to version 11.0.10, 10.1.44, or 9.0.108 (depending on your major version) to remediate this vulnerability.

Recommended fix High confidence

9.0.108 for 9.x, 10.1.44 for 10.1.x, or 11.0.10 for 11.x

  1. Identify your current Apache Tomcat major version (9.x, 10.x, or 11.x) by checking the VERSION file in the Tomcat installation directory or the server startup logs
  2. For Tomcat 9.x users: Upgrade to version 9.0.108 or later
  3. For Tomcat 10.1.x users: Upgrade to version 10.1.44 or later
  4. For Tomcat 11.x users: Upgrade to version 11.0.10 or later
  5. Download the corresponding binary distribution from https://tomcat.apache.org/
  6. Stop the Tomcat service or process
  7. Backup your existing Tomcat installation including conf/ directory and any custom configurations
  8. Extract the new version to your desired location
Caveat Minor version upgrades within the same Tomcat major version are typically backward compatible; review the release notes for any behavioral changes or deprecated features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tomcat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48989 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48989 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data