CVE-2026-41837

Spring Data REST Querydsl integration exposes Jackson-hidden persistent fields as filter keys

MEDIUM

5.3

CVSS Score

Published: June 9, 2026 at 11:49 PM UTC

Updated: July 23, 2026 at 07:32 PM UTC

2 products affected across 2 vendorsSpring Data RESTSpring Data REST

Using Spring Data REST by Spring?

Get instant alerts when new vulnerabilities affect Spring Data REST - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.3

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

Spring Data REST's Querydsl integration accepts arbitrary persistent property paths as request-parameter filter keys and does not consider Jackson customizations before handing them to Querydsl. Affected versions: Spring Data REST 3.7.0 through 3.7.19; 4.3.0 through 4.3.16; 4.4.0 through 4.4.14; 4.5.0 through 4.5.11; 5.0.0 through 5.0.5.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Spring Data REST · VMware

95%

3.7.0 ≤ v < 3.7.204.3.0 ≤ v < 4.3.174.4.0 ≤ v < 4.4.154.5.0 ≤ v < 4.5.11.15.0.0 ≤ v < 5.0.5.1

Affected range stops below 3.7.20, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.3.17, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.4.15, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.5.11.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.0.5.1, so it looks safe — our inference, not a vendor statement

Spring Data REST · Spring

60%

3.7.0 ≤ v < 3.7.204.3.0 ≤ v < 4.3.174.4.0 ≤ v < 4.4.154.5.0 ≤ v < 4.5.11.15.0.0 ≤ v < 5.0.5.13.7.0 4.3.0 4.4.0 4.5.0 5.0.0

Affected range stops below 3.7.20, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.3.17, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.4.15, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.5.11.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.0.5.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://spring.io/security/cve-2026-41837

References (1)

Vendor Advisory

Source: cverecord

https://spring.io/security/cve-2026-41837

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUMvmware

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: LOW
Integrity: NONE
Availability: NONE

Vector?

Quick Info

StatusANALYZED

CWE

CWE-284

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card