cve.bz

CVE-2026-41729 vmware spring data rest: Expression Language Injection

8.1 highEPSS 0.4%Fix available

High (8.1) in vmware spring data rest. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.data:spring-data-rest-core 4.5.12, 5.0.6.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-06-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-917 Improper Neutralization of Special Elements used in an Expression Language Statement (Expression Language Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-41729 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-41729?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-41729?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-41729 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring Data RESTfrom 3.7.0 before 3.7.20
Spring Data RESTfrom 4.3.0 before 4.3.17
Spring Data RESTfrom 4.4.0 before 4.4.15
Spring Data RESTfrom 4.5.0 before 4.5.12
Spring Data RESTfrom 5.0.0 before 5.0.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-j388-8rm5-p97fMavenorg.springframework.data:spring-data-rest-core>=5.0.0 <5.0.65.0.6
GHSA-j388-8rm5-p97fMavenorg.springframework.data:spring-data-rest-core>=4.5.0 <4.5.124.5.12
GHSA-j388-8rm5-p97fMavenorg.springframework.data:spring-data-rest-core>=4.4.0 <=4.4.14no fix published
GHSA-j388-8rm5-p97fMavenorg.springframework.data:spring-data-rest-core>=4.3.0 <=4.3.16no fix published
GHSA-j388-8rm5-p97fMavenorg.springframework.data:spring-data-rest-core<=3.7.19no fix published

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

References

Check your stackJSON