DE EN IT

~/exploited / cve-2016-3081

CVE-2016-3081: Apache Struts

According to CISA this vulnerability is already used in attacks (added on 8 October 2026).

Key facts

CVECVE-2016-3081
VendorApache — Struts
VulnerabilityApache Struts Command Injection Vulnerability
Added8 October 2026
Deadline (US agencies)11 October 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score8.1 (high) · CVSS 3.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack over the network, complexity: high, privileges: none needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 96.92%. Higher than 99.9% of all scored vulnerabilities (as of 18 November 2026). A high value means attacks are very likely and often already widespread.
Weakness type (CWE)CWE-77 — Command Injection
Affected versionsagile controller-campus firmware v100r002c00
anyoffice v200r005c00
anyoffice v200r006c00
logcenter v100r001c10
logcenter v100r001c20
firehunter6000 firmware v100r001c20
oceanstor 5300 v3 firmware v300r001
oceanstor 5300 v3 firmware v300r002
and 58 more

Description (NVD)

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.

Patches and vendor advisories

Description (CISA)

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.

Required action (CISA)

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.

What admins should do now

  1. Affected? Check whether Apache Struts is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 8 October 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).