Quick answers
- Is CVE-2026-59270 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59270 being exploited in the wild.
- How severe is CVE-2026-59270?
- Critical severity, with a CVSS score of 9.4, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring Security 5.7.0–5.7.25, 5.8.0–5.8.27, 6.4.0–6.4.18, 6.5.0–6.5.11, 7.0.0–7.0.6, 7.1.0.
- Is there a fix for CVE-2026-59270?
- 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-59270 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59270?
- Check whether you run VMware Spring Security 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 the UnboundIdContainer test utility used within Spring Security, which automatically registers administrative LDAP credentials without requiring configuration and binds its listener to 0.0.0.0 (all network interfaces). The root cause is insufficient access control and overly permissive network binding defaults. An unauthenticated attacker on the network can connect directly to the LDAP server port (typically 389 or 636) and authenticate as the administrative user with a known or discoverable password, gaining full directory privileges. This is an authentication bypass vulnerability in the embedded test LDAP server component. Patches are available for all affected versions.
Affected products
- VMware Spring Security 5.7.0–5.7.25, 5.8.0–5.8.27, 6.4.0–6.4.18, 6.5.0–6.5.11, 7.0.0–7.0.6, 7.1.0
Timeline
- 2026-08-27: disclosed