dbcve.org
Spring Data RestFramework / library · VMware

CVE-2026-41730

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 serializes the full exception cause chain into HTTP error response bodies, potentially exposing persistence-layer internals to HTTP clients. 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's default error handling serializes the complete exception cause chain into HTTP error responses, exposing internal persistence-layer details (database structure, query information, configuration) to clients.

MitigationUpgrade to Spring Data REST version 3.7.20, 4.3.17, 4.4.15, 4.5.12, or 5.0.6 or later, or implement a custom error handler that suppresses exception chain serialization.

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
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 checks

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

  1. Identify Spring Data REST dependency
    Review your project's build configuration (pom.xml, build.gradle, or equivalent) for spring-data-rest-core, spring-data-rest-webmvc, or spring-boot-starter-data-rest dependencies
    Affected if The dependency is present and the version falls within the affected 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. Determine the exact Spring Data REST version
    Check your dependency management or resolved dependencies to confirm the specific version number of spring-data-rest-core
    Affected if The resolved version matches any of the affected ranges listed above
  3. Verify REST repositories are exposed
    Inspect your repository interfaces for @RepositoryRestResource annotation or rely on Spring Data REST's default behavior of exposing all crud repositories as REST endpoints
    Affected if Any repository interface is exposed via Spring Data REST (either through @RepositoryRestResource or automatic exposure)
  4. Trigger an error to inspect response
    Send a request to an exposed REST endpoint that causes an error (for example, an invalid ID, a constraint violation, or malformed input) and examine the HTTP error response body
    Affected if The error response body contains full stack traces, nested exception messages, database queries, table names, or configuration details rather than a sanitized error message

You are affected if Spring Data REST is in use with a version matching the affected ranges AND REST repositories are exposed AND error responses expose stack traces or internal details.

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 Spring Data REST version 3.7.20, 4.3.17, 4.4.15, 4.5.12, or 5.0.6 or later, or implement a custom error handler that suppresses exception chain serialization.

Recommended fix High confidence

Spring Data REST 3.7.20, 4.3.17, 4.4.15, or 4.5.11.1 (depending on your major version branch)

  1. 1. Identify the current Spring Data REST version in your project by checking your build configuration (pom.xml for Maven or build.gradle for Gradle).
  2. 2. Determine which version branch your current installation belongs to (3.7.x, 4.3.x, 4.4.x, or 4.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. Update the version in your build configuration file (e.g., change spring-data-rest.version property or dependency version).
  8. 8. Rebuild and test your application to verify the fix works and no regressions are introduced.
Caveat Minor version upgrades within the same major-minor line typically have low breaking change risk; however, review release notes for any behavior changes in exception handling

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

Fix this in Spring Data Rest Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41730 — 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-41730 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