Apache Tomcat CVE-2025-61795
MEDIUMCVSS VectorNVD
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Lifecycle Timeline
2Blast Radius
ecosystem impact- 2 maven packages depend on org.apache.tomcat.embed:tomcat-embed-core (2 direct, 0 indirect)
- 2 maven packages depend on org.apache.tomcat:tomcat-catalina (2 direct, 0 indirect)
Ecosystem-wide dependent count for version 11.0.0-M1 and other introduced versions.
DescriptionNVD
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.
AnalysisAI
Denial of service in Apache Tomcat occurs when multipart upload errors leave temporary disk files uncleaned, allowing attackers to exhaust disk space faster than garbage collection reclaims it. Affected versions 8.5.0-8.5.100 (EOL), 9.0.0-M1-9.0.109, 10.1.0-M1-10.1.46, and 11.0.0-M1-11.0.11 require authenticated access (PR:L) and high attack complexity, making real-world exploitation limited despite the medium CVSS score.
Technical ContextAI
Apache Tomcat's multipart form data upload handler (RFC 2388) writes uploaded file parts to temporary disk storage during processing. The vulnerability lies in CWE-404 (Improper Resource Shutdown or Release), where exception handling during multipart processing fails to immediately delete temporary files. Instead of synchronous cleanup, Tomcat relies on Java garbage collection to invoke finalizers that remove these files. Under high load or with JVM settings that delay GC cycles, the rate of new temporary file creation can exceed the rate of GC-driven deletion, exhausting available disk space and causing service disruption. The condition is most severe when multipart limits are exceeded or parsing errors occur frequently, as each error leaves orphaned temporary files on disk.
RemediationAI
Upgrade to Apache Tomcat 9.0.110 or later, 10.1.47 or later, or 11.0.12 or later. For users unable to patch immediately, implement the following compensating controls with trade-offs: (1) Configure JVM heap and GC aggressively using flags such as '-XX:+UseG1GC -XX:MaxGCPauseMillis=50' to reduce GC delay, though this increases CPU overhead and latency; (2) Set strict multipart upload limits in Tomcat's connector configuration (maxPostSize, maxHttpHeaderSize) to reduce the likelihood of error conditions, but this may break legitimate large-file uploads; (3) Monitor disk usage on the Tomcat working directory (/path/to/catalina.base/work/) with alerting thresholds set to 80% capacity, enabling rapid detection and manual cleanup before DoS occurs; (4) Restrict multipart upload access to trusted internal networks via firewall rules, eliminating the network attack vector (AV:N) and converting the threat to local or authenticated-only. Consult https://lists.apache.org/thread/wm9mx8brmx9g4zpywm06ryrtvd3160pp for official guidance.
More from same product – last 7 days
Path traversal in Apache Ignite 2.0.0 through 2.17.0 lets authenticated REST API users read arbitrary files on the serve
Command injection in the shell-quote npm package allows attackers who can influence object-token inputs to inject arbitr
Heap buffer overflow in NGINX Plus and NGINX Open Source ngx_http_rewrite_module allows unauthenticated remote attackers
Code execution via Groovy sandbox bypass in Apache Syncope 3.0 through 3.0.16, 4.0 through 4.0.5, and 4.1.0 allows a hig
Default configurations of Apache Shiro have a session fixation vulnerability. This issue affects Apache Shiro from 1.0
Vendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today