CVE-2026-59333Spring Security Authentication Bypass by Spoofing
Spring
Vulnerability Summary
Spring Security IP Address CIDR Matching Ignores Address Family. Spring Security's IP address matching support, including IpAddressMatcher, IpAddressServerWebExchangeMatcher, and the InetAddressMatchers factory introduced in 7.1, matches a remote address against a configured IP address or CIDR range. When comparing addresses, the matcher compared only the leading bytes of the remote and configured addresses without first confirming that the two addresses belong to the same address family. Because IPv4 and IPv6 addresses have different byte lengths, a remote address in one family whose leading bytes happened to coincide with a configured CIDR range in the other family could be reported as a match even though the families differ. Preconditions: The application uses IpAddressMatcher, IpAddressServerWebExchangeMatcher, or InetAddressMatchers (for example via hasIpAddress(), an internal/external network check, or an include/exclude address list) to restrict access based on the remote IP address, and the application's network stack can present a remote address in an address family other than the one used in the matcher's configured address or CIDR range (for example through IPv4-mapped IPv6 addresses, a dual-stack listener, or a proxy that translates between families). An attacker connecting from an address family the application administrator did not intend to permit may be able to satisfy an IP-based access-control rule and bypass the restriction. Affected artifact: org.springframework.security:spring-security-core.
CVSS v3.1 Base Metrics — Score 7.4 (HIGH)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NAttack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
Affected & Patched Versions
- Spring Security 7.1.0 through 7.1.2
- Spring Security 7.1.3 (open source)
- Spring Security 7.1.2.1 (commercial support only)
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is high.
- Check whether you run Spring Security and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 19, 2026Published
- Nov 19, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Spring Security CVEsYou are reading CVE-2026-59333. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsRelated Coverage
More Spring Security CVEs
External References
- Vendor Advisoryhttps://spring.io/security/cve-2026-59333
Data last checked: Nov 20, 2026 05:01 UTC