How severe is GHSA-36p3-wjmg-h94x?

GHSA-36p3-wjmg-h94x has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-36p3-wjmg-h94x?

GHSA-36p3-wjmg-h94x affects the following packages: org.springframework:spring-beans (Maven), org.springframework:spring-beans (Maven), org.springframework:spring-webmvc (Maven), org.springframework:spring-webmvc (Maven), org.springframework.boot:spring-boot-starter-web (Maven), org.springframework.boot:spring-boot-starter-web (Maven), org.springframework:spring-webflux (Maven), org.springframework:spring-webflux (Maven), and 2 more. Ecosystems affected: Maven.

How do I fix GHSA-36p3-wjmg-h94x?

Update org.springframework:spring-beans to 5.2.20.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-36p3-wjmg-h94x is resolved across your whole dependency graph.

How do I detect GHSA-36p3-wjmg-h94x in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-beans, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-36p3-wjmg-h94x if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-36p3-wjmg-h94x actively exploited in the wild?

Yes. There are 106 known exploit references for GHSA-36p3-wjmg-h94x, including 50 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-36p3-wjmg-h94x?

GHSA-36p3-wjmg-h94x has an EPSS (Exploit Prediction Scoring System) score of 99.6%, 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.

Is GHSA-36p3-wjmg-h94x in the CISA Known Exploited Vulnerabilities catalog?

Yes. GHSA-36p3-wjmg-h94x (Spring Framework JDK 9+ Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-04-04. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-04-25. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is GHSA-36p3-wjmg-h94x?

GHSA-36p3-wjmg-h94x is classified as Code Injection (CWE-94). 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-36p3-wjmg-h94x?

A Nuclei detection template exists for GHSA-36p3-wjmg-h94x, meaning automated scanners can fingerprint it. 2 Metasploit modules reference GHSA-36p3-wjmg-h94x, 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-36p3-wjmg-h94x published, and has it been updated?

GHSA-36p3-wjmg-h94x was published on March 31, 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

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

Remote Code Execution in Spring FrameworkGHSA-36p3-wjmg-h94x

CRITICALFix: spring-projects/spring-framework@002546b

GHSA-36p3-wjmg-h94x is a critical-severity (CVSS 9.8) Code Injection vulnerability in org.springframework:spring-beans. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-04-04) — treat it as actively exploited and patch now. A fix is available for org.springframework:spring-beans — see the affected versions and patch details below.

Also known asCVE-2022-22965

Published

Mar 31, 2022

Updated

Oct 22, 2025

Affected

10 pkgs

Patched

10 / 10

Exploits

106 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-04-04. Federal agencies were required to remediate by 2022-04-25.
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 (KEV catalog and SSVC triage) for GHSA-36p3-wjmg-h94x.

EPSS Exploitation Probability

via FIRST.org ↗

99.6%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

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-36p3-wjmg-h94x by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

10 pkgs affected

☕org.springframework:spring-beans☕org.springframework:spring-beans☕org.springframework:spring-webmvc☕org.springframework:spring-webmvc☕org.springframework.boot:spring-boot-starter-web☕org.springframework.boot:spring-boot-starter-web☕org.springframework:spring-webflux☕org.springframework:spring-webflux+2 more

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

Spring Framework prior to versions 5.2.20 and 5.3.18 contains a remote code execution vulnerability known as Spring4Shell.

Impact

A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding. The specific exploit requires the application to run on Tomcat as a WAR deployment. If the application is deployed as a Spring Boot executable jar, i.e. the default, it is not vulnerable to the exploit. However, the nature of the vulnerability is more general, and there may be other ways to exploit it.

These are the prerequisites for the exploit:

JDK 9 or higher
Apache Tomcat as the Servlet container
Packaged as WAR
spring-webmvc or spring-webflux dependency

Patches

Spring Framework 5.3.18 and 5.2.20
Spring Boot 2.6.6 and 2.5.12

Workarounds

For those who are unable to upgrade, leaked reports recommend setting disallowedFields on WebDataBinder through an @ControllerAdvice. This works generally, but as a centrally applied workaround fix, may leave some loopholes, in particular if a controller sets disallowedFields locally through its own @InitBinder method, which overrides the global setting.

To apply the workaround in a more fail-safe way, applications could extend RequestMappingHandlerAdapter to update the WebDataBinder at the end after all other initialization. In order to do that, a Spring Boot application can declare a WebMvcRegistrations bean (Spring MVC) or a WebFluxRegistrations bean (Spring WebFlux).

Affected Packages

10 total 10 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework:spring-beans`	all versions	5.2.20.RELEASE`org.springframework:spring-beans:5.2.20.RELEASE`
☕Maven	`org.springframework:spring-beans`	≥ 5.3.0&&< 5.3.18	5.3.18`org.springframework:spring-beans:5.3.18`
☕Maven	`org.springframework:spring-webmvc`	all versions	5.2.20.RELEASE`org.springframework:spring-webmvc:5.2.20.RELEASE`
☕Maven	`org.springframework:spring-webmvc`	≥ 5.3.0&&< 5.3.18	5.3.18`org.springframework:spring-webmvc:5.3.18`
☕Maven	`org.springframework.boot:spring-boot-starter-web`	all versions	2.5.12`org.springframework.boot:spring-boot-starter-web:2.5.12`
☕Maven	`org.springframework.boot:spring-boot-starter-web`	≥ 2.6.0&&< 2.6.6	2.6.6`org.springframework.boot:spring-boot-starter-web:2.6.6`

Affected Products

38 products · 97 configurations

Application

cx cloud agentcisco

< 2.1.0

range

Application

commerce platformoracle

1 version

11.3.2

Application

communications cloud native core automated test suiteoracle

2 versions

1.9.022.1.0

Application

communications cloud native core binding support functionoracle

1 version

22.1.3

Application

communications cloud native core consoleoracle

2 versions

1.9.022.1.0

Application

communications cloud native core network exposure functionoracle

1 version

22.1.0

Exploits & PoCs

106

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