CVE-2025-61795: Apache Tomcat: Delayed cleaning of multi-part upload temporary files may lead to DoS

Published Oct 27, 2025
·
Updated

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.

Other sources

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 denial-of-service (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 End of Life (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.

— F5

Affected Software

20 affected componentsFixes available
Apache Tomcat>=11.0.0-M1<=11.0.11, >=10.1.0-M1<=10.1.46, >=9.0.0.M1<=9.0.109, >=8.5.0<=8.5.100
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.5.60<=8.5.100
maven/org.apache.tomcat.embed:tomcat-embed-core>=9.0.0.40<9.0.110
9.0.110
maven/org.apache.tomcat.embed:tomcat-embed-core>=10.1.0-M1<10.1.47
10.1.47
maven/org.apache.tomcat.embed:tomcat-embed-core>=11.0.0-M1<11.0.12
11.0.12
maven/org.apache.tomcat:tomcat-catalina>=8.5.60<=8.5.100
maven/org.apache.tomcat:tomcat-catalina>=9.0.0.40<9.0.110
9.0.110
maven/org.apache.tomcat:tomcat-catalina>=10.1.0-M1<10.1.47
10.1.47
maven/org.apache.tomcat:tomcat-catalina>=11.0.0-M1<11.0.12
11.0.12
maven/org.apache.tomcat:tomcat>=8.5.60<=8.5.100
maven/org.apache.tomcat:tomcat>=9.0.0.40<9.0.110
9.0.110
maven/org.apache.tomcat:tomcat>=10.1.0-M1<10.1.47
10.1.47
maven/org.apache.tomcat:tomcat>=11.0.0-M1<11.0.12
11.0.12
F5 Traffix SDC=5.2.0
Apache Tomcat>=8.5.0<=8.5.100
Apache Tomcat>=9.0.0<9.0.110
Apache Tomcat>=10.0.0<10.0.27
Apache Tomcat>=10.1.0<10.1.47
Apache Tomcat>=11.0.0<11.0.12
IBM API Connect V12 OnPrem<=All

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 9.0.110
  2. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 10.1.47
  3. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 11.0.12
  4. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 9.0.110
  5. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 10.1.47
  6. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 11.0.12
  7. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.110
  8. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.47
  9. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.12
  10. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.12
  11. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.47
  12. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.110

Event History

Oct 27, 2025
CVE Published
via MITRE·05:30 PM
Data Sourced
via MITRE·05:30 PM
DescriptionWeakness
Data Sourced
via Red Hat·06:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
Affected Software
Advisory Published
via GitHub·06:31 PM
Data Sourced
via GitHub·06:31 PM
DescriptionWeaknessAffected Software
Nov 14, 2025
Advisory Published
via F5·01:10 AM
Data Sourced
via F5·01:10 AM
DescriptionSeverityWeaknessAffected Software
Jul 7, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-61795?

CVE-2025-61795 has been classified with a moderate severity level due to potential resource leakage.

2

How do I fix CVE-2025-61795?

To fix CVE-2025-61795, upgrade to Apache Tomcat version 11.0.12 or higher, 10.1.47 or higher, 9.0.110 or higher, or 8.5.101 or higher.

3

Which versions of Apache Tomcat are affected by CVE-2025-61795?

CVE-2025-61795 affects Apache Tomcat versions from 8.5.0 to 8.5.100, 9.0.0-M1 to 9.0.109, 10.1.0-M1 to 10.1.46, and 11.0.0-M1 to 11.0.11.

4

What type of vulnerability is CVE-2025-61795?

CVE-2025-61795 is classified as an Improper Resource Shutdown or Release vulnerability.

5

What is the consequence of not addressing CVE-2025-61795?

Failing to address CVE-2025-61795 may lead to undetected temporary files occupying disk space, potentially affecting system performance.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203