Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8Exploited · CISA KEV

Code execution in Apache Struts 1 plugin

CVE-2017-9791GHSA-29rm-6752-gvwv

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven org.apache.struts:struts2-struts1-plugin

    Affected
    <= 2.3.37
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
Confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H
EPSS
  • CVE-2017-9791: 98.91% estimated exploitation activity in the next 30 days; percentile 99.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

The Struts 1 plugin used with Apache Struts 2.1.x and 2.3.x might allow remote code execution via a malicious field value passed in a raw message to the ActionMessage.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-29rm-6752-gvwv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2017-9791

Advisory: Code execution in Apache Struts 1 plugin
IDs: CVE-2017-9791, GHSA-29rm-6752-gvwv
Record: https://patchnext.com/advisories/cve-2017-9791 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.struts:struts2-struts1-plugin: affected <= 2.3.37

## Suggested inspection (read-only)
- Maven org.apache.struts:struts2-struts1-plugin: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.struts:struts2-struts1-plugin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (CISA added CVE-2017-9791 to the Known Exploited Vulnerabilities catalog on 2022-02-10.)
- Verified: https://github.com/advisories/GHSA-29rm-6752-gvwv (GitHub-reviewed advisory GHSA-29rm-6752-gvwv lists affected ranges: Maven org.apache.struts:struts2-struts1-plugin >=0 <=2.3.37)

Commands are suggestions: review each one before running it.

Loading voting…