CVE-2025-61795: Improper Resource Shutdown or Release vulnerability in Apache Tomcat.
Medium CVSS 5.3
- CVE id
- CVE-2025-61795
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Apache Tomcat Runtimes and servers |
>= 8.5.0, <= 8.5.100 >= 9.0.0, < 9.0.110 >= 10.0.0, < 10.0.27 >= 10.1.0, < 10.1.47 >= 11.0.0, < 11.0.12 |
9.0.110, 10.0.27, 10.1.47, 11.0.12 |
How to fix it
Upgrade Apache Tomcat to the fixed release of the line you run: 9.0.110, 10.0.27, 10.1.47, 11.0.12.
catalina.sh version
- Install the patched Tomcat release of your branch (the tomcat image tag, or your tomcat packages) and restart it.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
Improper Resource Shutdown or Release vulnerability in Apache Tomcat.
If an error occurred (including exceeding limits) during the processing of a multipart upload, temporary copies of the uploaded parts written to disc were not cleaned up immediately but left for the garbage collection process to delete. Depending on JVM settings, application memory usage and application load, it was possible that space for the temporary copies of uploaded parts would be filled faster than GC cleared it, leading to a DoS.
This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.11, from 10.1.0-M1 through 10.1.46, from 9.0.0.M1 through 9.0.109.
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.12 or later, 10.1.47 or later or 9.0.110 or later which fixes the issue.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.