dbcve.org
Spring Data RestFramework / library · VMware

CVE-2026-41729

HIGH · 8.1 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 3.7.20 / 4.3.17 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Spring Data REST is vulnerable to SpEL expression injection through map-typed properties when processing JSON Patch (application/json-patch+json) requests. When a persistent entity exposes a Map-typed property, the JSON Pointer path segment used as the map key is embedded directly into a SpEL expression without sanitization or validation. 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 confidence

Spring Data REST is vulnerable to SpEL expression injection when processing JSON Patch requests on entities with Map-typed properties. The JSON Pointer path segment used as the map key is directly concatenated into a SpEL expression without sanitization, allowing attackers to inject arbitrary SpEL expressions that could result in remote code execution.

MitigationUpgrade to a patched version of Spring Data REST (4.5.12+, 5.0.6+, or newer). If immediate upgrade is not feasible, disable JSON Patch support for endpoints exposing entities with Map-typed properties and implement strict input validation on JSON Pointer paths.

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
Affected:>= 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.1

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Data REST version
    Check your project dependencies (Maven pom.xml, Gradle build.gradle, or the spring-data-rest-core JAR manifest) for the spring-data-rest-core or spring-data-rest version
    Affected if The version falls within any of these ranges: 3.7.0-3.7.19, 4.3.0-4.3.16, 4.4.0-4.4.14, 4.5.0-4.5.11, or 5.0.0-5.0.5
  2. Confirm JSON Patch endpoint exposure
    Inspect your REST controllers and entity definitions to determine if any controller exposes endpoints that process PATCH requests (application/json-patch+json) or if Spring Data REST's default JSON Patch support is active
    Affected if PATCH requests with Content-Type application/json-patch+json are accepted on any REST endpoint backed by a Spring Data REST repository
  3. Identify Map-typed properties in entities
    Review your persistent entity classes that are exposed via Spring Data REST repositories. Look for fields or properties declared as java.util.Map or implementation types like HashMap, LinkedHashMap, etc.
    Affected if Any exposed entity contains a Map-typed property that is accessible through the REST endpoint (even if not explicitly exposed, default accessors may be reachable)
  4. Verify Map property exposure via REST
    Test by sending a GET request to the entity's collection endpoint and examine the JSON response, or inspect the repository's exposure configuration. Map-typed properties are exposed by default unless explicitly hidden via @JsonIgnore or RepositoryRestResource(excludedPaths=)
    Affected if The Map-typed property appears in the JSON response from the REST endpoint and the key could be supplied by an attacker

You are affected if your Spring Data REST version is within the vulnerable ranges AND you have Map-typed properties in entities exposed via REST endpoints that accept JSON Patch (PATCH) requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.7.20 / 4.3.17 / 4.4.15 or later
Fixed in 3.7.204.3.174.4.15
Interim mitigation

Upgrade to a patched version of Spring Data REST (4.5.12+, 5.0.6+, or newer). If immediate upgrade is not feasible, disable JSON Patch support for endpoints exposing entities with Map-typed properties and implement strict input validation on JSON Pointer paths.

Recommended fix High confidence

Upgrade to the first fixed version in your current major branch: 3.7.20, 4.3.17, 4.5.11.1, or 5.0.6 respectively

  1. 1. Identify the current Spring Data REST version in your project (check pom.xml or build.gradle for spring-data-rest.version or spring-boot-starter-data-rest version)
  2. 2. Determine which major version line you are using (3.x, 4.x, or 5.x)
  3. 3. For Spring Data REST 3.7.x: upgrade to version 3.7.20 or later
  4. 4. For Spring Data REST 4.3.x: upgrade to version 4.3.17 or later
  5. 5. For Spring Data REST 4.4.x: upgrade to version 4.4.15 or later
  6. 6. For Spring Data REST 4.5.x: upgrade to version 4.5.11.1 or later
  7. 7. For Spring Data REST 5.x: upgrade to version 5.0.6 or later
  8. 8. Update the version in your build configuration file (pom.xml, build.gradle, or equivalent)
Caveat Minor patch upgrade; unlikely to have breaking changes. However, always review release notes for any behavior changes in JSON Patch handling.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Data Rest Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41729 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41729 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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