StrutsFramework / library · Apache
CVE-2025-66675
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 · uneditedDenial of Service vulnerability in Apache Struts, file leak in multipart request processing causes disk exhaustion. This issue affects Apache Struts: from 2.0.0 through 6.7.4, from 7.0.0 through 7.0.3. Users are recommended to upgrade to version 6.8.0 or 7.1.1, which fixes the issue. It's related to https://cve.org/CVERecord?id=CVE-2025-64775 - this CVE addresses missing affected version 6.7.4
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 Struts contains a file leak vulnerability in its multipart request processing. When handling multipart form data uploads, temporary files are created but not properly cleaned up after processing. An attacker can exploit this by sending repeated multipart requests, causing disk space to be exhausted and leading to 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
StrutsFramework / library
>= 2.0.0, <= 2.3.37>= 2.5.0, <= 2.5.33>= 6.0.0, < 6.8.0>= 7.0.0, < 7.1.1CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 the installed Apache Struts versionLocate the struts2-core JAR file in your application lib directory and check its filename version (for example, struts2-core-2.5.33.jar), or query your build configuration (Maven pom.xml, Gradle build.gradle) for the struts2-core dependency versionAffected if The version falls within any of these ranges: 2.0.0 to 2.3.37, 2.5.0 to 2.5.33, 6.0.0 to 6.7.x, or 7.0.0 to 7.1.0
-
Confirm multipart form data upload is in useReview your Struts action configurations (struts.xml or annotations) for the enctype="multipart/form-data" attribute on form tags, or check for any action classes that handle file uploads using org.apache.struts2.interceptor.FileUploadInterceptor or similarAffected if Multipart file upload is enabled and your application accepts file upload requests from users or external systems
-
Inspect for leftover temporary filesCheck the default temporary directory (system property java.io.tmpdir, commonly /tmp on Linux or C:\Users\...\AppData\Local\Temp on Windows) for files matching the pattern 'struts_upload_*' or 'upload_*' that persist after requests completeAffected if Temporary upload files accumulate and are not deleted after request processing completes, indicating the file leak is active in your environment
-
Monitor disk space consumptionTrack disk usage on the partition where the temporary directory resides, particularly monitoring for rapid growth in the temp folder size correlated with incoming multipart requestsAffected if Disk space steadily decreases over time without other explanations, especially in the temp directory used by the application server
You are affected if your Apache Struts version is 2.0.0-2.3.37, 2.5.0-2.5.33, 6.0.0-6.7.x, or 7.0.0-7.1.0 AND your application processes multipart form data uploads, as this combination enables the file leak vulnerability to manifest.
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 · scoped6.8.07.1.1
Upgrade to Apache Struts version 6.8.0 or 7.1.1 which contains the fix for this file leak vulnerability. As an interim measure, implement rate limiting or restrictions on multipart request processing at the load balancer or web server level.
6.8.0 (for Struts 6.x) or 7.1.1 (for Struts 7.x)
- 1. Identify the currently running Struts version by checking your project dependencies (Maven pom.xml, Gradle build file, or library manifests)
- 2. Determine which major version line you are on (Struts 2.x, 6.x, or 7.x)
- 3. For Struts 6.x users: upgrade to version 6.8.0 or later
- 4. For Struts 7.x users: upgrade to version 7.1.1 or later
- 5. For Struts 2.x users (2.0.0-2.3.37 or 2.5.0-2.5.33): no explicit fixed version mentioned; consider migrating to supported Struts 6.x or 7.x branches
- 6. Update your dependency management file (e.g., pom.xml) with the new version number
- 7. Rebuild and test your application to verify the upgrade does not break existing functionality
- 8. Deploy the updated application
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Struts
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66675 — 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-66675 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