CVE-2016-3081
KEVApache Struts Command Injection Vulnerability
Description
Apache Struts contains a command injection vulnerability that could allow remote attackers to execute arbitrary code via method:prefix when Dynamic Method Invocation is enabled.
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.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HPublishedApr 26, 2016
Last modifiedOct 9, 2026
Added to KEVOct 8, 2026
Remediation dueOct 11, 2026
References
- packetstormsecurity.com/files/136856/Apache-Struts-2.3.28-Dynamic-Method-Invocation-Remote-Code-Execution.htmlExploitThird Party Advisory
- huawei.com/en/psirt/security-advisories/huawei-sa-20160527-01-struts2-enThird Party Advisory
- oracle.com/technetwork/security-advisory/cpujul2016-2881720.htmlPatchThird Party Advisory
- oracle.com/technetwork/security-advisory/cpuoct2016-2881722.htmlThird Party Advisory
- rapid7.com/db/modules/exploit/linux/http/struts_dmi_execThird Party AdvisoryBroken Link
- rapid7.com/db/modules/exploit/multi/http/struts_dmi_execThird Party Advisory
- securityfocus.com/bid/87327Third Party AdvisoryVDB Entry
- securityfocus.com/bid/91787Third Party AdvisoryVDB Entry
- securitytracker.com/id/1035665Third Party AdvisoryVDB Entry
- struts.apache.org/docs/s2-032.htmlPatchVendor Advisory
- exploit-db.com/exploits/39756/ExploitThird Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2016-3081US Government Resource
0 recent articles mention this CVE
80
Risk assessment · Critical
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 15 days
- CVSS
- 8.1 HIGH
- EPSS (30-day exploit probability)
- 96.5% · top 1% of all CVEs
- Weakness
- CWE-77
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
Recommended actions
- 1.Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.