Spring Data RestFramework / library · VMware
CVE-2026-41837
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSpring 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSpring Data REST's Querydsl integration accepts arbitrary persistent property paths as request-parameter filter keys without validating them against Jackson customizations. This allows attackers to potentially access internal or private entity properties by crafting filter parameters that bypass property exposure restrictions that Jackson would normally enforce.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Spring Data RestFramework / library
>= 3.7.0, < 3.7.20>= 4.3.0, < 4.3.17>= 4.4.0, < 4.4.15>= 4.5.0, < 4.5.11.1>= 5.0.0, < 5.0.5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Spring Data REST versionInspect your project's dependency manifest (pom.xml, build.gradle, or the spring-data-rest-core jar META-INF/MANIFEST.MF) to find the Spring Data REST version in useAffected if The installed version falls within any of these ranges: >= 3.7.0 and < 3.7.20; >= 4.3.0 and < 4.3.17; >= 4.4.0 and < 4.4.15; >= 4.5.0 and < 4.5.11.1; >= 5.0.0 and < 5.0.5.1
-
Confirm Querydsl integration is in useSearch for QuerydslRepositorySupport, QuerydslPredicateExecutor, or Q-classes (generated Querydsl query types) in your codebase or runtime classpathAffected if Your application uses Querydsl with Spring Data REST repositories, enabling dynamic property path filtering via request parameters
-
Verify REST endpoints expose Querydsl query parametersReview your Spring Data REST exported repository interfaces for QuerydslPredicateExecutor or custom controller methods that accept query parameters for filteringAffected if Your REST API accepts arbitrary property paths as query parameters that could bypass Jackson serialization restrictions
-
Identify sensitive properties with Jackson restrictionsInspect your entity classes for properties annotated with @JsonIgnore, @JsonIgnoreProperties, or similar Jackson visibility controls that should restrict serializationAffected if You have entity properties with Jackson serialization restrictions that could be circumvented through Querydsl property path access
You are affected if your Spring Data REST version is within the affected ranges AND you use Querydsl integration with exposed REST endpoints, allowing attackers to bypass Jackson annotations on sensitive entity properties.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.7.204.3.174.4.15
Upgrade Spring Data REST to version 3.7.20, 4.3.17, 4.4.15, 4.5.12, 5.0.6, or later. If immediate upgrade is not feasible, restrict or disable Querydsl integration endpoints through Spring Data REST configuration.
Spring Data REST 3.7.20+, 4.3.17+, 4.4.15+, 4.5.11.1+ (or 5.0.6+ if using 5.x)
- 1. Identify the current Spring Data REST version in your project by checking your build configuration (Maven pom.xml or Gradle build.gradle)
- 2. Determine which version branch your current version belongs to (3.7.x, 4.3.x, 4.4.x, or 4.5.x)
- 3. For Spring Data REST 3.7.x: upgrade to version 3.7.20 or later
- 4. For Spring Data REST 4.3.x: upgrade to version 4.3.17 or later
- 5. For Spring Data REST 4.4.x: upgrade to version 4.4.15 or later
- 6. For Spring Data REST 4.5.x: upgrade to version 4.5.11.1 or later
- 7. For Spring Data REST 5.x (if applicable): upgrade to version 5.0.6 or later if available
- 8. Update the version in your build configuration file
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Data Rest
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41837 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41837 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data