Advisory record · GHSA-mwpv-rg79-863c

Spring Data REST Querydsl Integration Exposes Persistent Property Paths, Bypassing Jackson Customizations

CVSS 5.3 MediumEPSS 0.0019 · 8th percentile

Published by the GitHub Advisory Database at 10 Jun 2026, 00:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.springframework.data:spring-data-rest-coreMaven>=5.0.0, <5.0.6 || >=4.5.0, <4.5.12 || >=4.4.0, <=4.4.14 || >=4.3.0, <=4.3.16 || <=3.7.195.0.6, 4.5.12
Identifiers
GHSA-mwpv-rg79-863c · CVE-2026-41837
Weakness (CWE)
CWE-284
Published
10 Jun 2026
Updated
12 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Spring Data REST's Querydsl integration (org.springframework.data:spring-data-rest-core) accepts arbitrary persistent property paths as request-parameter filter keys and does not apply Jackson customizations before passing them to Querydsl. Affected versions are 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. The source does not describe what an attacker must do beyond sending crafted request parameters, or the resulting impact. Upgrade to 5.0.6 or 4.5.12, or to a release line that is not affected.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N CNA (vmware)
  • CISA KEV Not listed.
  • EPSS 0.0019, the 8th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.