dbcve.org
StrutsFramework / library · Apache

CVE-2025-64775

HIGH · 7.5 CVSS v3.1 Published 2025-12-01
Fix available
A fix is available. Upgrade to 6.8.0 / 7.1.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Denial 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.0, 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.

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 confidence

A file leak vulnerability in Apache Struts' multipart request processing allows attackers to cause disk exhaustion by uploading files that are not properly cleaned up after request processing. This leads to denial of service through consumed disk space.

MitigationUpgrade Apache Struts to version 6.8.0 or 7.1.1. As a compensating control, implement file size limits and temporary file cleanup policies for multipart requests.

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
Affected:>= 2.0.0, < 6.8.0>= 7.0.0, < 7.1.1

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Struts version
    Locate the Struts library JAR file in your application's classpath or dependencies (e.g., struts2-core.jar) and check its version metadata, or run 'mvn dependency:tree' or inspect your build configuration to list the struts2-core version
    Affected if The version is 2.0.0 or higher but below 6.8.0, or 7.0.0 or higher but below 7.1.1
  2. Verify multipart request handling is in use
    Search your application code and configuration for 'struts.multipart' settings in struts.xml or struts.properties, and check if any forms or endpoints use 'enctype="multipart/form-data"'
    Affected if Multipart form uploads are enabled or used in your application (the vulnerability only affects environments handling file uploads)
  3. Inspect temp directory for leftover files
    Locate the directory configured for temporary file storage (check 'struts.multipart.saveDir' setting or default temp location like /tmp or the servlet container's work directory) and list files to see if older upload artifacts remain after requests complete
    Affected if Multiple temporary files from past uploads exist and are not being cleaned up after request processing
  4. Review disk space consumption
    Monitor disk usage on the partition hosting your application's temp directory over time, particularly after periods of heavy file upload activity
    Affected if Disk space is progressively consumed and correlates with application upload traffic without being reclaimed

You are affected if your Apache Struts version falls within the vulnerable ranges AND your application processes multipart file uploads, as the flaw allows temp files to accumulate and consume disk space.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.8.0 / 7.1.1 or later
Fixed in 6.8.07.1.1
Interim mitigation

Upgrade Apache Struts to version 6.8.0 or 7.1.1. As a compensating control, implement file size limits and temporary file cleanup policies for multipart requests.

Recommended fix High confidence

6.8.0 (for Struts 2.x) or 7.1.1 (for Struts 7.x)

  1. Identify the current Struts version in your project's dependency configuration (pom.xml, build.gradle, or manifest)
  2. Determine which major version line you are using (Struts 2.x or 7.x)
  3. Update the Struts dependency version to 6.8.0 (for Struts 2.x users) or 7.1.1 (for Struts 7.x users)
  4. Rebuild the application with the updated dependency
  5. Run existing tests to verify functionality after the upgrade
  6. Deploy the rebuilt application to your environment
Caveat Major version upgrades may include API changes; review release notes for breaking changes between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Struts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64775 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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