CVE-2018-11776

CRITICALNVD 8.19.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.1 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 8.1 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild

Also known asEUVD-2018-0582 (ENISA EUVD) · GHSA-cr6j-3jp9-rw65 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: >99.9%CVSS: 8.1Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is available — apply it.

Apache Struts versions 2.3 to 2.3.34 and 2.5 to 2.5.16 suffer from possible Remote Code Execution when alwaysSelectFullNamespace is true (either by user or a plugin like Convention Plugin) and then: results are used with no namespace and in same time, its upper package have no or wildcard namespace and similar to results, same possibility when using url tag which doesn't have value and action set and in same time, its upper package have no or wildcard namespace.

CVSS v3
8.1
EG Score
9.0CRITICALhigh confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
>99.9%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 8.1 HIGH.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
>99.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2018-11776

Published

August 22, 2018

Last Modified

October 27, 2025

Advisory Details (6)

Auto-updated Nov 2, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available.
Web page

GitHub - hook-s3c/CVE-2018-11776-Python-PoC: Working Python test and PoC for CVE-2018-11776, includes Docker lab · GitHub

https://github.com/hook-s3c/CVE-2018-11776-Python-PoC
Web page

S2-057 - Apache Struts 2 Wiki - Apache Software Foundation

https://cwiki.apache.org/confluence/display/WW/S2-057
Web page

PSIRT.COM — Product Security Incident Response Team

http://www.securityfocus.com/bid/105125

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.apache.struts:struts2-core @ 2.3.35 (fixes >= 2.0.4, <= 2.3.34)—ghsa
mavenorg.apache.struts:struts2-core @ 2.5.17 (fixes >= 2.5, <= 2.5.16)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.struts:struts2-core2.5 ... 2.5.8 (12 versions)
  • 2.0.4 up to 2.3.35: fixed in 2.3.35
  • 2.5 up to 2.5.17: fixed in 2.5.17
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 122 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 24 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 19:55 UTCOSV refresh
  2. 2026-11-02 02:53 UTCEG score recompute
  3. 2026-11-02 02:52 UTCGHSA enrichmentGHSA-cr6j-3jp9-rw65 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-11-01 08:43 UTCGHSA enrichmentGHSA-cr6j-3jp9-rw65 · GitHub severity HIGH · GitHub CVSS 8.1
  5. 2026-11-01 08:43 UTCEG score recompute
  6. 2026-11-01 04:13 UTCEG score recompute
  7. 2026-10-31 05:31 UTCEG score recompute
  8. 2026-10-30 06:52 UTCEG score recompute
  9. 2026-10-29 08:13 UTCEG score recompute
  10. 2026-10-28 09:35 UTCEG score recompute
  11. 2026-10-27 16:27 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  12. 2026-10-27 10:54 UTCEG score recompute
  13. 2026-10-25 19:26 UTCEG score recompute
  14. 2026-10-25 16:27 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  15. 2026-10-25 13:34 UTCEG score recompute
  16. 2026-10-24 14:55 UTCEG score recompute
  17. 2026-10-22 17:36 UTCEG score recompute
  18. 2026-10-21 18:55 UTCEG score recompute
  19. 2026-10-20 20:17 UTCEG score recompute
  20. 2026-10-20 16:27 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  21. 2026-10-19 21:38 UTCEG score recompute
  22. 2026-10-18 22:59 UTCEG score recompute
  23. 2026-10-18 10:22 UTCEG score recompute
  24. 2026-10-18 00:19 UTCEG score recompute
  25. 2026-10-17 01:40 UTCEG score recompute
Show 73 more
  1. 2026-10-16 03:01 UTCEG score recompute
  2. 2026-10-15 04:20 UTCEG score recompute
  3. 2026-10-14 05:38 UTCEG score recompute
  4. 2026-10-12 20:20 UTCEG score recompute
  5. 2026-10-11 21:22 UTCEG score recompute
  6. 2026-10-11 17:42 UTCEG score recompute
  7. 2026-10-11 14:01 UTCEG score recompute
  8. 2026-09-28 21:32 UTCEG score recompute
  9. 2026-09-27 21:51 UTCCISA KEV update
  10. 2026-09-25 19:35 UTCCISA KEV update
  11. 2026-09-25 14:55 UTCCISA KEV update
  12. 2026-09-24 19:31 UTCCISA KEV update
  13. 2026-09-22 19:36 UTCCISA KEV update
  14. 2026-09-21 19:09 UTCCISA KEV update
  15. 2026-09-18 19:20 UTCCISA KEV update
  16. 2026-09-18 14:15 UTCCISA KEV update
  17. 2026-09-16 14:10 UTCCISA KEV update
  18. 2026-09-14 19:24 UTCCISA KEV update
  19. 2026-09-11 18:49 UTCCISA KEV update
  20. 2026-09-10 19:28 UTCCISA KEV update
  21. 2026-09-09 19:08 UTCCISA KEV update
  22. 2026-09-08 18:54 UTCCISA KEV update
  23. 2026-09-04 17:38 UTCCISA KEV update
  24. 2026-09-04 06:01 UTCEG score recompute
  25. 2026-09-04 05:02 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  26. 2026-09-02 17:33 UTCCISA KEV update
  27. 2026-08-31 14:19 UTCCISA KEV update
  28. 2026-08-29 01:07 UTCEG score recompute
  29. 2026-08-28 21:36 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  30. 2026-08-27 17:22 UTCCISA KEV update
  31. 2026-08-26 17:41 UTCCISA KEV update
  32. 2026-08-24 18:52 UTCCISA KEV update
  33. 2026-08-24 15:46 UTCEG score recompute
  34. 2026-08-23 03:37 UTCEG score recompute
  35. 2026-08-23 00:14 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  36. 2026-08-21 16:49 UTCCISA KEV update
  37. 2026-08-20 17:06 UTCCISA KEV update
  38. 2026-08-19 17:33 UTCCISA KEV update
  39. 2026-08-18 16:58 UTCCISA KEV update
  40. 2026-08-17 13:56 UTCCISA KEV update
  41. 2026-08-16 05:12 UTCEG score recompute
  42. 2026-08-16 02:10 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  43. 2026-08-11 19:32 UTCCISA KEV update
  44. 2026-08-07 17:09 UTCCISA KEV update
  45. 2026-08-05 17:25 UTCCISA KEV update
  46. 2026-08-04 17:02 UTCCISA KEV update
  47. 2026-08-03 19:22 UTCCISA KEV update
  48. 2026-07-30 11:58 UTCEG score recompute
  49. 2026-07-29 19:27 UTCCISA KEV update
  50. 2026-07-27 19:24 UTCCISA KEV update
  51. 2026-07-27 17:17 UTCCISA KEV update
  52. 2026-07-26 13:37 UTCEG score recompute
  53. 2026-07-26 02:26 UTCEG score recompute
  54. 2026-07-24 14:14 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  55. 2026-07-23 01:32 UTCEG score recompute
  56. 2026-07-22 22:12 UTCEG score recompute
  57. 2026-07-22 19:40 UTCCISA KEV update
  58. 2026-07-21 14:37 UTCCISA KEV update
  59. 2026-07-17 10:16 UTCEG score recompute
  60. 2026-07-16 17:04 UTCCISA KEV update
  61. 2026-07-16 16:59 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  62. 2026-07-15 16:49 UTCCISA KEV update
  63. 2026-07-15 15:04 UTCCISA KEV update
  64. 2026-07-14 18:05 UTCCISA KEV update
  65. 2026-07-13 17:07 UTCCISA KEV update
  66. 2026-07-10 17:52 UTCCISA KEV update
  67. 2026-07-07 19:01 UTCCISA KEV update
  68. 2026-07-07 17:16 UTCCISA KEV update
  69. 2026-07-01 19:16 UTCCISA KEV update
  70. 2026-06-29 19:12 UTCCISA KEV update
  71. 2026-06-28 14:04 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  72. 2026-06-25 19:15 UTCCISA KEV update
  73. 2026-06-25 13:47 UTCEPSS rescoreEPSS >99.9% · 99th percentile

Publicly available exploits

(15 references, 10 shown)

Public exploit code is referenced for this CVE (1 Metasploit module, 3 Exploit-DB entries, 10 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-45367✓ verified
    Published Sep 10, 2018

    Apache Struts 2 - Namespace Redirect OGNL Injection (Metasploit)

    Open source ↗
  • Metasploitexploit/multi/http/struts2_namespace_ognl✓ verified
    Published Sep 7, 2018

    Apache Struts 2 Namespace Redirect OGNL Injection

    Open source ↗
  • Nucleihttp/cves/2018/CVE-2018-11776.yaml
    Published Mar 5, 2021

    Apache Struts2 S2-057 - Remote Code Execution

    Open source ↗
  • GitHub PoCarlyone/Apache-Struts-0Day-Exploit
    Published Oct 10, 2019

    Critical Remote Code Execution Vulnerability (CVE-2018-11776) Found in Apache Struts.

    Open source ↗
  • GitHub PoC649/Apache-Struts-Shodan-Exploit
    Published Aug 29, 2018

    This tool takes advantage of CVE-2018-11776 and Shodan to perform mass exploitation of verified and vulnerable Apache Struts servers.

    Open source ↗
  • GitHub PoCbrianwrf/S2-057-CVE-2018-11776
    Published Aug 28, 2018

    A simple exploit for Apache Struts RCE S2-057 (CVE-2018-11776)

    Open source ↗
  • GitHub PoCEkultek/Strutter
    Published Aug 27, 2018

    Proof of Concept for CVE-2018-11776

    Open source ↗
  • Exploit-DBEDB-45260
    Published Aug 26, 2018

    Apache Struts 2.3 < 2.3.34 / 2.5 < 2.5.16 - Remote Code Execution (1)

    Open source ↗
  • Exploit-DBEDB-45262
    Published Aug 25, 2018

    Apache Struts 2.3 < 2.3.34 / 2.5 < 2.5.16 - Remote Code Execution (2)

    Open source ↗
  • GitHub PoCbhdresh/CVE-2018-11776
    Published Aug 25, 2018

    Vulnerable docker container for CVE-2018-11776

    Open source ↗

Frequently asked(6)

What is CVE-2018-11776?
CVE-2018-11776 is a critical-severity vulnerability; its CVE record was published on August 22, 2018. Apache Struts versions 2.3 to 2.3.34 and 2.5 to 2.5.16 suffer from possible Remote Code Execution when alwaysSelectFullNamespace is true (either by user or a plugin like Convention Plugin) and then: results are used with no namespace and in same time, its upper package have no or wildcard namespace…
When was CVE-2018-11776 made public?
CVE-2018-11776 was made public on August 22, 2018: that is the date its CVE record's CNA, Apache Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on August 22, 2018. EchelonGraph's copy of the record carries a last-modified date of October 27, 2025; the record at its source may have been updated since.
Is CVE-2018-11776 actively exploited?
Yes. CISA added CVE-2018-11776 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Apache Struts. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2018-11776?
CVE-2018-11776 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2018-11776?
CVE-2018-11776 affects Apache Struts. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2018-11776?
A fix for CVE-2018-11776 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-11776

Explore →

Is Your Infrastructure Affected by CVE-2018-11776?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.