A flaw was found in Keycloak’s WebAuthn registration component. This vulnerability allows an attacker to bypass the configured attestation policy and register untrusted or forged authenticators via submission of an attestation object with fmt: "none", even when the realm is configured to require direct attestation. This can lead to weakened authentication integrity and unauthorized authenticator registration.
Security readout for executives and security teams
Plain-English summary
Keycloak can accept a WebAuthn authenticator registration that should be rejected by policy. If a realm requires direct attestation, an attacker may still register an untrusted or forged authenticator using an attestation object marked as none. This weakens assurance around phishing-resistant authentication, but the reported severity is low and user interaction is required.
Executive priority
Handle through normal patch management, with higher priority for identity platforms protecting privileged or regulated access. This is not currently an emergency signal, but identity assurance weaknesses can undermine MFA trust if your organization depends on attestation enforcement.
Technical view
CVE-2025-12150 is a CWE-347 verification flaw in Keycloak WebAuthn registration. The configured attestation policy can be bypassed when an attestation object uses fmt: none despite direct attestation being required. Red Hat rates it CVSS 3.1, vector AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N.
Likely exposure
Exposure is most relevant to Red Hat build of Keycloak 26.2 and 26.4 deployments using WebAuthn with direct attestation requirements. The bundle lists specific affected rhbk Keycloak, operator, and operator-bundle packages. Upstream Keycloak is listed with default status unaffected in the provided data.
Exploitation context
No CISA KEV listing or cited source indicates active exploitation. Exploitation requires a registration flow and user interaction, and impacts authentication integrity rather than confidentiality or availability. The business concern is reduced trust in enrolled WebAuthn authenticators where attestation policy is relied upon.
Researcher notes
The provided record names a policy bypass in WebAuthn registration, not account takeover by itself. Public evidence in the bundle does not show exploitation in the wild. Validate affectedness against Red Hat package versions and advisories; avoid assuming all Keycloak deployments are vulnerable.
Mitigation direction
Apply the relevant Red Hat security advisory updates for affected Keycloak builds.
Prioritize environments requiring WebAuthn direct attestation for high-assurance access.
Check Red Hat and Keycloak guidance for version-specific remediation details.
Review whether affected realms depend on attestation for authenticator trust decisions.
Validation and detection
Inventory Red Hat build of Keycloak 26.2 and 26.4 deployments.
Compare installed rhbk package versions with the affected and unaffected versions listed by Red Hat.
Identify realms with WebAuthn enabled and direct attestation required.
Review recent WebAuthn registrations for unexpected none-format attestation acceptance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-347 · source CWE mapping
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.