Skip to content
Server Security Center
KEVhigh8.1

CVE-2016-3081: Apache Struts Command Injection

Apache Struts · listed in the CISA catalog of actively exploited vulnerabilities since 2026-10-08.

CVSS v3.1 (CISA ADP)
8.1
high
EPSS (exploit probability, 30 days)
97%
higher than 99.8% of all CVEs
Added to CISA KEV
2026-10-08
US federal due date 2026-10-11
Automatable (CISA SSVC)
no
technical impact: total

CVE-2016-3081 explained

CVE-2016-3081 is a command injection vulnerability in Apache Struts. When Dynamic Method Invocation is enabled, remote attackers can execute arbitrary code through the method: prefix, related to chained expressions. CISA lists it as known to be exploited, so affected servers need prompt attention.

Impact

A remote attacker without credentials or user interaction can execute arbitrary code on an affected Struts application, but only when Dynamic Method Invocation is enabled. Attack complexity is high. Successful exploitation can fully compromise confidentiality, integrity and availability. CISA rates the technical impact as total and the vulnerability as not automatable. CISA reports active exploitation. Ransomware use is unknown.

Who is affected

The description names Apache Struts 2.3.19 to 2.3.20.2, 2.3.21 to 2.3.24.1, and 2.3.25 to 2.3.28 as affected when Dynamic Method Invocation is enabled. The structured CVE record lists no affected versions. It also names no fixed version. Check the vendor advisory to find out which release contains the fix.

Written with AI from the data on this page and checked against it automatically.

Official description

Apache Struts 2.3.19 to 2.3.20.2, 2.3.21 to 2.3.24.1, and 2.3.25 to 2.3.28, when Dynamic Method Invocation is enabled, allow remote attackers to execute arbitrary code via method: prefix, related to chained expressions.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: struts.apache.org/docs/s2-032.html
  • CISA's deadline for US federal agencies: 2026-10-11 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Identify all Apache Struts applications and check whether they run a version named in the description.
  2. Follow the Apache vendor advisory and upgrade to the fixed release it identifies.
  3. Disable Dynamic Method Invocation where it is not required.
  4. Restrict internet exposure of affected Struts applications until they are updated or mitigated.
  5. Check affected servers for signs of compromise, following CISA's forensics triage requirements.

The CVE record names no fixed version. Follow the Apache vendor advisory for the fixed release and its mitigations, and disable Dynamic Method Invocation where possible. CISA requires applying mitigations per vendor instructions and following BOD 26-04 guidance. If mitigations are unavailable, CISA says to discontinue use of the product.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-77 Improper Neutralization of Special Elements used in a Command ('Command Injection')

Questions about CVE-2016-3081

Is every Struts deployment of these versions exploitable?
According to the description, the vulnerability applies only when Dynamic Method Invocation is enabled. Deployments of the listed versions should still be updated.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-10-08, with a US federal due date of 2026-10-11. Ransomware use is unknown.
Which version fixes it?
The CVE record names no fixed version. Consult the Apache vendor advisory for the fixed release.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.