How severe is GHSA-jc35-q369-45pv?

GHSA-jc35-q369-45pv has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jc35-q369-45pv?

GHSA-jc35-q369-45pv affects the following packages: org.apache.struts:struts2-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-jc35-q369-45pv?

Update org.apache.struts:struts2-core to 2.5.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jc35-q369-45pv is resolved across your whole dependency graph.

How do I detect GHSA-jc35-q369-45pv in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.struts:struts2-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-jc35-q369-45pv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-jc35-q369-45pv?

O3 pinpoints whether GHSA-jc35-q369-45pv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-jc35-q369-45pv actively exploited in the wild?

Yes. There are 14 known exploit references for GHSA-jc35-q369-45pv, including 8 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-jc35-q369-45pv?

GHSA-jc35-q369-45pv has an EPSS (Exploit Prediction Scoring System) score of 95.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-jc35-q369-45pv?

GHSA-jc35-q369-45pv is classified as Expression Language Injection (CWE-917). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-jc35-q369-45pv?

A Nuclei detection template exists for GHSA-jc35-q369-45pv, meaning automated scanners can fingerprint it. 2 Metasploit modules reference GHSA-jc35-q369-45pv, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-jc35-q369-45pv published, and has it been updated?

GHSA-jc35-q369-45pv was published on February 9, 2022 and was last updated on October 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

GHSA-jc35-q369-45pv

CRITICAL

GHSA-jc35-q369-45pv is a critical-severity (CVSS 9.8) Expression Language Injection vulnerability in org.apache.struts:struts2-core. 14 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-jc35-q369-45pv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Remote code execution in Apache Struts

Also known asCVE-2020-17530

Published

Feb 9, 2022

Updated

Oct 22, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

14 known

Exploitation data as of Sep 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

CISA’s SSVC triage classifies this CVE as under active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-jc35-q369-45pv.

EPSS Exploitation Probability

via FIRST.org ↗

95.9%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-jc35-q369-45pv plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.

Where this sits among everything scored

Of 0 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected

☕org.apache.struts:struts2-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Forced OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.struts:struts2-core`	≥ 2.0.0&&< 2.5.26	2.5.26

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.