CVE Watchtower

CVE-2026-59330Spring Security

Spring

Vulnerability Summary

WebAuthn Signature Counter Check Fails to Detect Cloned Authenticators. Spring Security's WebAuthn relying-party support, Webauthn4JRelyingPartyOperations, does not effectively enforce its authenticator signature-counter check. WebAuthn authenticators are expected to increment a per-credential signature counter on every use, and a relying party is expected to reject an assertion whose counter fails to increase, since a counter that repeats or regresses is a strong signal that the authenticator has been cloned. An internal defect in how Webauthn4JRelyingPartyOperations supplies the previously stored counter to the underlying verification library means this check does not actually detect a non-incrementing counter, so this defense-in-depth control against cloned authenticators is not effective. Preconditions: The application uses Webauthn4JRelyingPartyOperations (Spring Security's default WebAuthn RelyingPartyOperations implementation) to authenticate users. An attacker has obtained a cloned or otherwise duplicated WebAuthn authenticator capable of producing valid assertions for a credential already registered to a victim. An attacker who already possesses such a cloned authenticator can continue to authenticate as the victim without Spring Security detecting or rejecting the clone. Affected artifact: org.springframework.security:spring-security-webauthn.
Severity Level
HIGH(7.4)
Published Date
Nov 19, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Reserved
This CVE ID is referenced in a public advisory, but the CVE Program has not published its official CVE Record yet. Full CVSS/CPE data from NVD will appear here once it does.
Root Weakness (CWE)
See the MITRE CWE entry for the full definition of this weakness.
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:N
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • Spring Security 7.1.0 through 7.1.2
  • Spring Security 7.0.0 through 7.0.8
Patched Versions
  • Spring Security 7.1.3 (open source)
  • Spring Security 7.0.9 (open source)
  • Spring Security 7.1.2.1 (commercial support only)
  • Spring Security 7.0.8.1 (commercial support only)

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run Spring Security and which version.
  2. 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-59330. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More Spring Security CVEs

External References

Data last checked: Nov 20, 2026 05:01 UTC