CVE-2026-41837

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

Published Jun 9, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Spring Data REST’s Querydsl integration accepts arbitrary persistent property paths as filter keys without respecting Jackson customizations that hide certain fields. This oversight enables an attacker to request data fields that should be hidden, potentially exposing sensitive internal data. The flaw is rooted in improper access control (CWE‑284) and can let attackers learn more about the application’s data model than intended.

Affected Systems

Affected are Spring Data REST releases 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, and 5.0.0 through 5.0.5. Users of these versions that expose REST endpoints powered by Querydsl are impacted.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity; the EPSS score is not available and the vulnerability is not listed in CISA KEV catalog. The attack can be performed via an HTTP request to a REST endpoint, by supplying an arbitrary filter key that maps to a hidden property. Successful exploitation would read otherwise protected data, affecting confidentiality of the application’s information resources.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Spring Data REST to the latest available release or to any version released after 3.7.19, 4.3.16, 4.4.14, 4.5.11, or 5.0.5.
  • Configure Jackson to enforce hidden properties on all exposed endpoints or apply additional property filtering rules.
  • Disable Querydsl filter support on sensitive REST endpoints or add explicit authorization checks for exposed filter keys.

Generated by OpenCVE AI on June 10, 2026 at 01:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-mwpv-rg79-863c Spring Data REST Querydsl Integration Exposes Persistent Property Paths, Bypassing Jackson Customizations
References
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Spring
Spring spring Data Rest
Vendors & Products Spring
Spring spring Data Rest
Type Values Removed Values Added
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.
Title Spring Data REST Querydsl integration exposes Jackson-hidden persistent fields as filter keys
Weaknesses CWE-284
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Jun 30, 2026, 9:47 PM
Reserved
Apr 22, 2026, 6:22 AM
Status
Analyzed
Published
Jun 10, 2026, 12:16 AM
Modified
Jul 23, 2026, 9:10 AM