TomcatWeb server / proxy · Apache
CVE-2025-61795
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 · uneditedImproper 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.
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 confidenceApache Tomcat fails to immediately delete temporary files created during multipart upload processing when errors occur (including limit exceedances). Instead, these files rely on JVM garbage collection for cleanup, allowing disk space to fill faster than it can be reclaimed and causing a denial of service.
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
>= 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.12CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Apache Tomcat is your web serverCheck the server response headers (look for 'Server: Apache-Coyote/1.1' or 'Server: Apache Tomcat') or check running processes for 'catalina.jar' or the 'catalina.sh' scriptAffected if Apache Tomcat is in use as the web container
-
Determine the installed Tomcat versionCheck the 'serverinfo.txt' file in the Tomcat lib directory, or look at the ' RELEASE-NOTE' file in the Tomcat home directory, or run: java -cp catalina.jar org.apache.catalina.util.ServerInfoAffected if The version falls within these ranges: 8.5.0-8.5.100, 9.0.0-9.0.110, 10.0.0-10.0.27, 10.1.0-10.1.47, or 11.0.0-11.0.12
-
Confirm multipart upload handling is in useCheck your web application's configuration for file upload forms (enctype='multipart/form-data') or check if the application uses Servlet 3.0+ file upload APIs or Apache Commons FileUploadAffected if The application processes multipart HTTP requests for file uploads
-
Locate and inspect the Tomcat temp directoryCheck the 'catalina.sh' or 'setenv.sh' for the 'java.io.tmpdir' setting, or look at the default temp directory (typically $CATALINA_HOME/temp or /tmp); examine the directory for numerous temporary files with patterns like 'upload_' or 'multipart_'Affected if The temp directory contains orphaned temporary files from failed uploads that are not being cleaned up promptly
-
Monitor disk space growth on the temp directory partitionUse 'df -h' on the partition containing the temp directory over time, or use 'du -sh <temp_dir>' to track directory size growth, especially after file upload errorsAffected if Disk space on the temp partition is consumed faster than expected or grows without bound after upload errors occur
You are affected if you run a Tomcat version in the affected range AND your application processes multipart file uploads, as failed uploads will leave temporary files that are not promptly cleaned up, leading to potential disk space exhaustion.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.0.11010.0.2710.1.47
Upgrade to Apache Tomcat 9.0.110+, 10.1.47+, or 11.0.12+ which implements immediate cleanup of temporary multipart files on error, or implement external cleanup processes for the temp directory.
Tomcat 9.0.110 or later (9.0.x branch), Tomcat 10.1.47 or later (10.1.x branch), or Tomcat 11.0.12 or later (11.x branch)
- Back up your current Tomcat installation including all configuration files and deployed applications
- Download the appropriate fixed version for your Tomcat branch (9.0.110, 10.1.47, or 11.0.12) from the official Apache Tomcat downloads page
- Stop the running Tomcat instance
- Replace the Tomcat installation files with the new version, preserving your configuration files (server.xml, context.xml, etc.)
- Review the release notes for the new version to ensure any configuration changes are applied
- Deploy your applications if not preserving the entire installation
- Start Tomcat and verify the service is running correctly
- Test multipart upload functionality to confirm the fix is working
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Tomcat
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61795 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-61795 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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