Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-p5mm-xwgq-whfr

Spring Data REST potentially exposes persistence-layer internals to HTTP clients

CVSS 5.3 MediumEPSS 0.0020 · 9th 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-p5mm-xwgq-whfr · CVE-2026-41730
Weakness (CWE)
CWE-209
Tags
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 (spring-data-rest-core) versions 3.7.19 and earlier, 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 serialize the full exception cause chain into HTTP error response bodies. A remote client that sends requests to the application can see persistence-layer internals in those error responses. Upgrade to 5.0.6 or 4.5.12, or to the fixed version on your release line. The source gives few details on the exact conditions that trigger this.

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.0020, the 9th percentile, on 9 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.