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. 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 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 pinpoints whether CVE-2022-22980 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 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 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 July 15, 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

CVE-2022-22980

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. O3 Security confirms whether CVE-2022-22980 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

SpEL Injection in Spring Data MongoDB

Also known asGHSA-w24x-87mr-4r23

Published

Jun 22, 2022

Updated

Jul 15, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

13 known

Blast Radius

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
☕Maven	`org.springframework.data:spring-data-mongodb`	all versions	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.