Skip to main content
VulnerabilityPublished Updated

CVE-2023-41835: Apache Struts · Incomplete Cleanup

Affects Apache StrutsSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
7.3% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Dec 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.apache.struts/struts2-corepkg:maven/org.apache.struts/struts2-coreOther threatsAffected
  • =2.0.0
  • =6.1.2.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade Apache Struts to versions 2.5.32, 6.1.2.2, 6.3.0.1, or later to remediate this vulnerability. In addition to patching, organizations should implement monitoring of the struts.multipart.saveDir directory to detect abnormal file accumulation indicative of exploitation attempts. Automated cleanup scripts or scheduled tasks can be employed as a temporary mitigation to remove orphaned files and prevent disk exhaustion. Web application firewalls (WAFs) can be configured to limit the size of multipart requests or block requests with fields exceeding expected length thresholds. Organizations should also review and tighten maxStringLength configurations to reasonable limits based on application requirements. Regular audits of disk usage and alerting on unusual spikes can help detect early signs of exploitation. Finally, integrating vulnerability scanning and patch management processes will ensure timely detection and remediation of similar issues in the future.

Description

When a Multipart request is performed but some of the fields exceed the maxStringLength  limit, the upload files will remain in struts.multipart.saveDir  even if the request has been denied. Users are recommended to upgrade to versions Struts 2.5.32 or 6.1.2.2 or Struts 6.3.0.1 or greater, which fixe this issue.

References

Community reviews

Loading reviews…