Skip to content
Fencer Vulns
critical 9.8

CVE-2022-22980 in the critical feed json

SpEL Injection in Spring Data MongoDB

published 2022-06-22 4 y ago modified 2026-06-17 4 mo ago also GHSA-w24x-87mr-4r23 , EUVD-2022-6169

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
17.8%
EPSS 17.8% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.springframework.data:spring-data-mongodb 3.3.5, 3.4.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-22980 updated cvss 9.8

MongoDB: SpEL in query methods allow code injection

  • Red Hat Integration Camel K 1 spring-data-mongodb spring-data-mongodb
    affected: no fix planned “Will not fix”
  • Red Hat Fuse 7 spring-data-mongodb spring-data-mongodb
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

17.84% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.1 9.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.springframework.data:spring-data-mongodb
>=3.4.0, <3.4.1
<3.3.5
3.4.1
3.3.5

Affected products

  • n/a Spring Data MongoDB

Classification

Weakness
  • CWE-917 Improper Neutralization of Special Elements used in an Expression Language Statement

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.