CVE-2025-66675
Apache Struts 2.0.0 – 2.3.37
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:HSummary
CVE-2025-66675 is a high-severity Incomplete Cleanup (CWE-459) vulnerability in Apache Struts. Its CVSS base score is 8.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 45th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-14 (Non-persistence) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-66675 is a denial-of-service vulnerability in Apache Struts stemming from a file leak during multipart request processing, which can lead to disk exhaustion. The issue affects Apache Struts versions from 2.0.0 through 6.7.4 and from 7.0.0 through 7.0.3. It has a CVSS v3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H) and is associated with CWE-459 (Incomplete Cleanup).
A remote, unauthenticated attacker can exploit this vulnerability over the network with low complexity and no user interaction required. By sending crafted multipart requests, the attacker triggers incomplete file cleanup, causing files to accumulate on disk and exhaust storage resources, resulting in high availability impact and potential service disruption. A low confidentiality impact is also possible due to leaked files.
Apache recommends upgrading to version 6.8.0 or 7.1.1, which address the issue. This CVE supplements CVE-2025-64775 by including the previously missing affected version 6.7.4. Additional details are available in the Apache Struts security advisory at https://cwiki.apache.org/confluence/display/WW/S2-068 and the related CVE record at https://cve.org/CVERecord?id=CVE-2025-64775.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-202417
Vulnerability Data
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.4, from 7.0.0 through 7.0.3. Users are recommended to upgrade to version 6.8.0 or 7.1.1, which…
more
fixes the issue. It's related to https://cve.org/CVERecord?id=CVE-2025-64775 - this CVE addresses missing affected version 6.7.4
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.4.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover incomplete cleanup through dynamic analysis or resource-leak testing.
Non-persistence mechanisms explicitly initiate resources in a known state and terminate them, directly enforcing cleanup.
Session termination forces explicit release of session-related temporary resources.
Preventing unintended information transfer through shared resources requires complete cleanup of those resources.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices and coding standards normally require proper resource release and cleanup.
Life-cycle management encompasses disposal of temporary resources but does not specifically target runtime cleanup bugs.
Explicitly calls for removing sensitive data after use, directly addressing one class of incomplete cleanup.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Explicitly requires secure deletion of temporary or residual data, directly addressing incomplete cleanup.
SDLC practices include cleanup steps, yet the weakness can still occur if those steps are omitted.
Secure-coding rules can mandate explicit cleanup of temporary resources, but do not guarantee it.
Change-management processes may require cleanup verification, but the control itself does not address the weakness.