CVE-2025-12150
Attestation Bypass in Keycloak WebAuthn Enables Unauthorized Registration
Publication date: 2026-02-27
Last updated on: 2026-03-05
Assigner: Red Hat, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| redhat | build_of_keycloak | * |
| redhat | keycloak | 24.0.2 |
| redhat | build_of_keycloak | to 26.4.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-347 | The product does not verify, or incorrectly verifies, the cryptographic signature for data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a flaw in Keycloak's WebAuthn registration component that allows an attacker to bypass the configured attestation policy. Specifically, it enables the registration of untrusted or forged authenticators by submitting an attestation object with the format "none", even when the system is set to require direct attestation. This means attackers can register authenticators that should normally be rejected, weakening the authentication process.
How can this vulnerability impact me? :
The impact of this vulnerability is that it can weaken authentication integrity by allowing unauthorized authenticators to be registered. This could potentially enable attackers to gain unauthorized access by using forged or untrusted authenticators, thereby compromising the security of the authentication system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know