How severe is GHSA-v8j6-6c2r-r27c?

GHSA-v8j6-6c2r-r27c has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-v8j6-6c2r-r27c?

GHSA-v8j6-6c2r-r27c affects the following packages: org.apache.struts:struts2-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-v8j6-6c2r-r27c?

Update org.apache.struts:struts2-core to 2.5.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v8j6-6c2r-r27c is resolved across your whole dependency graph.

How do I detect GHSA-v8j6-6c2r-r27c 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-v8j6-6c2r-r27c 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-v8j6-6c2r-r27c?

O3 pinpoints whether GHSA-v8j6-6c2r-r27c 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-v8j6-6c2r-r27c actively exploited in the wild?

Yes. There are 9 known exploit references for GHSA-v8j6-6c2r-r27c, including 7 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 type of vulnerability is GHSA-v8j6-6c2r-r27c?

GHSA-v8j6-6c2r-r27c 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-v8j6-6c2r-r27c?

A Nuclei detection template exists for GHSA-v8j6-6c2r-r27c, meaning automated scanners can fingerprint it. 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-v8j6-6c2r-r27c published, and has it been updated?

GHSA-v8j6-6c2r-r27c was published on April 13, 2022 and was last updated on February 20, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-v8j6-6c2r-r27c

CRITICAL

Expression Language Injection in Apache Struts

Also known asCVE-2021-31805

Published

Apr 13, 2022

Updated

Feb 20, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

9 known

Blast Radius

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

The fix issued for CVE-2020-17530 was incomplete. So from Apache Struts 2.0.0 to 2.5.29, still some of the tag’s attributes could perform a double evaluation if a developer applied forced OGNL evaluation by using the %{...} syntax. Using forced OGNL evaluation on untrusted user input can lead to a Remote Code Execution and security degradation.

Affected Packages

1 total 1 fixed

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

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.