Quick answers
- Is CVE-2026-59277 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59277 being exploited in the wild.
- How severe is CVE-2026-59277?
- Low severity, with a CVSS score of 3.7, published 27 August 2026.
- Which products and versions are affected?
- Spring Spring Security 7.1.0.
- Is there a fix for CVE-2026-59277?
- 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-59277 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59277?
- Check whether you run VMware Spring Security. 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 Security's InetAddressMatchers utility, which provides matchInternal() and matchExternal() builders for constructing an InetAddressMatcher that classifies IP addresses as belonging to internal (private) or external (public) networks. The root cause appears to be a flaw in the IP classification logic that incorrectly categorizes certain IP addresses. An attacker with network access can send requests with specially crafted IP addresses to bypass IP-based access controls. This affects applications relying on Spring Security's IP address matching for network segmentation or geo-based restrictions.
Affected products
- Spring Spring Security 7.1.0
Timeline
- 2026-08-27: disclosed