CVE-2026-47850: Spring Data REST allows mutation of the version property of immutable aggregates via PUT
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: spring data rest 3.7.21; spring data rest 4.4.16; spring data rest 4.5.13; spring data rest 5.0.6.1; spring data rest 5.1.0.1 upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
Spring Data REST does not preserve the persisted version (@Version) property of an aggregate root when handling an HTTP PUT against an immutable target type. Spring Data REST 5.1.0 Spring Data REST 5.0.0 - 5.0.6 Spring Data REST 4.5.0 - 4.5.12 Spring Data REST 4.0.0 - 4.4.15 Spring Data REST 3.7.20 and earlier
- weakness
- CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
- affected
- Spring Data REST
- published ranges
- vmware spring data rest < 3.7.21; vmware spring data rest >= 4.0.0 < 4.4.16; vmware spring data rest >= 4.5.0 < 4.5.13; vmware spring data rest >= 5.0.0 < 5.0.6.1; and 1 more on the CVE page
- first unaffected version, by branch
- spring data rest 3.7.21; spring data rest 4.4.16; spring data rest 4.5.13; spring data rest 5.0.6.1; spring data rest 5.1.0.1
- severity
- 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- assigned by
- vmware
- published
- 2026-08-26
check us spring.io
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 28 Aug 2026 | 0.00179 | |
| 5 Sep 2026 | 0.00183 | |
| 28 Sep 2026 | 0.00306 |
3 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-09-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: spring data rest 3.7.21; spring data rest 4.4.16; spring data rest 4.5.13; spring data rest 5.0.6.1; spring data rest 5.1.0.1. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-47850', '2026-10-29T23:59:59.999999Z', now());