Skip to main content
Mallory
MediumVulnerability

CVE-2025-61795: Apache Tomcat Multipart Upload Temporary File Cleanup Denial of Service

Published Oct 27, 2025 · Updated 23 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS5.3Medium · v3.1
EPSS1.3%70th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Apache Software Foundation
IdentifiersCVE-2025-61795CWE-404 · Improper Resource Shutdown or…

Apache Tomcat fails to immediately delete temporary files containing uploaded multipart parts when upload processing encounters an error, including when configured limits are exceeded. Cleanup is instead deferred to garbage collection. Depending on JVM settings, application memory usage, and application load, temporary files can accumulate faster than garbage collection removes them, exhausting available storage and causing denial of service. Affected versions are 11.0.0-M1 through 11.0.11, 10.1.0-M1 through 10.1.46, and 9.0.0.M1 through 9.0.109. The end-of-life 8.5.0 through 8.5.100 releases are also affected; older unsupported releases may be affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Accumulation of temporary multipart-upload files can exhaust the storage available to Tomcat and disrupt application availability. Successful exploitation can cause denial of service without requiring confidentiality or integrity compromise.

Mitigation

If you can’t patch tonight, do this now.

Until upgrading, restrict access to multipart-upload functionality, rate-limit upload requests, and monitor temporary-upload storage usage with alerting and operational cleanup procedures. Enforce request size and part limits at an upstream layer where possible; Tomcat-side upload limits alone do not prevent exploitation because exceeding limits can trigger the vulnerable error handling. These measures reduce exposure but do not correct the cleanup defect.

Remediation

Patch, then assume compromise.

Upgrade Apache Tomcat to 11.0.12 or later, 10.1.47 or later, or 9.0.110 or later in the corresponding supported branch. Migrate affected Tomcat 8.5 installations and older unsupported releases to a supported, fixed branch. For products embedding Tomcat, apply the product vendor's update that incorporates the fix.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationTomcatapplication
FAQ

Frequently asked questions

Is CVE-2025-61795 exploited in the wild?
Yes. As of Oct 25, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2025-61795?
As of Oct 25, 2026, Mallory has found no public exploit for CVE-2025-61795.
Is there a patch for CVE-2025-61795?
Upgrade Apache Tomcat to 11.0.12 or later, 10.1.47 or later, or 9.0.110 or later in the corresponding supported branch. Migrate affected Tomcat 8.5 installations and older unsupported releases to a supported, fixed branch.
What products are affected by CVE-2025-61795?
Apache Software Foundation Tomcat.
How severe is CVE-2025-61795?
CVE-2025-61795 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 1.3% (70th percentile) as of Oct 25, 2026.
Activity feed

Recent activity

28 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+1 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.