How severe is CVE-2022-22980?

CVE-2022-22980 has a CVSS score of 9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-22980?

CVE-2022-22980 affects the following packages: org.springframework.data:spring-data-mongodb (Maven), org.springframework.data:spring-data-mongodb (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-22980?

Update org.springframework.data:spring-data-mongodb to 3.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-22980 is resolved across your whole dependency graph.

How do I detect CVE-2022-22980 in my Maven dependencies?

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

How do I mitigate CVE-2022-22980 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 CVE-2022-22980?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-22980 can be triaged on real exposure rather than presence alone.

Is CVE-2022-22980 actively exploited in the wild?

Yes. There are 13 known exploit references for CVE-2022-22980, 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 is the EPSS score for CVE-2022-22980?

CVE-2022-22980 has an EPSS (Exploit Prediction Scoring System) score of 17.8%, placing it in the 97th 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. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2022-22980?

CVE-2022-22980 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.

When was CVE-2022-22980 published, and has it been updated?

CVE-2022-22980 was published on June 22, 2022 and was last updated on August 12, 2026. 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

CVE-2022-22980 — spring-data-mongodb

CRITICAL

CVE-2022-22980 is a critical-severity (CVSS 9) Expression Language Injection vulnerability in org.springframework.data:spring-data-mongodb. 13 public exploit references exist, so weaponization risk is real. A fix is available for org.springframework.data:spring-data-mongodb — see the affected versions and patch details below.

SpEL Injection in Spring Data MongoDB

Also known asGHSA-w24x-87mr-4r23

Published

Jun 22, 2022

Updated

Aug 12, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

13 known

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

EPSS Exploitation Probability

via FIRST.org ↗

17.8%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% 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

CVE-2022-22980 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

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

Real-World Exposure

2 pkgs affected

☕org.springframework.data:spring-data-mongodb☕org.springframework.data:spring-data-mongodb

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

A Spring Data MongoDB application is vulnerable to SpEL Injection when using @Query or @Aggregation-annotated query methods with SpEL expressions that contain query parameter placeholders for value binding if the input is not sanitized.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.data:spring-data-mongodb`	≥ 3.4.0&&< 3.4.1	3.4.1`org.springframework.data:spring-data-mongodb:3.4.1`
☕Maven	`org.springframework.data:spring-data-mongodb`	all versions	3.3.5`org.springframework.data:spring-data-mongodb:3.3.5`

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.