Quick answers
- Is CVE-2026-47850 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47850 being exploited in the wild.
- How severe is CVE-2026-47850?
- Medium severity, with a CVSS score of 4.3, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring Data REST 5.1.0, 5.0.0–5.0.6, 4.5.0–4.5.12, 4.0.0–4.4.15, 3.7.20 and earlier.
- Is there a fix for CVE-2026-47850?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-47850 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47850?
- Check whether you run VMware Spring Data REST at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in Spring Data REST's HTTP PUT handler for immutable entity types. When processing a PUT request against an aggregate root marked with @Version (used for optimistic locking), the framework does not preserve the persisted version property during serialization/deserialization. The root cause is improper handling of immutable target types during entity update operations. An attacker with network access to a REST endpoint can craft concurrent PUT requests to exploit optimistic locking bypass, potentially causing data inconsistency or lost updates. The issue affects multiple versions across the 3.x, 4.x, and 5.x release lines; patches are expected from the Spring team.
Affected products
- VMware Spring Data REST 5.1.0, 5.0.0–5.0.6, 4.5.0–4.5.12, 4.0.0–4.4.15, 3.7.20 and earlier
Timeline
- 2026-08-27: disclosed