CVE-2026-8830: Keycloak: org.keycloak/keycloak-services: keycloak: policy bypass during webauthn credential registration via client-side javascript manipulation
A flaw was found in Keycloak. An authenticated user can bypass configured WebAuthn policies during credential registration by manipulating client-side JavaScript. This occurs because the server-side processAction() fails to validate that the newly created credential's parameters, such as public key algorithms, match the realm's configured WebAuthn policies. This could lead to the creation of credentials that do not adhere to administrative security requirements, potentially weakening the overall security posture of the system by allowing non-compliant authentication methods.
Security readout for executives and security teams
Plain-English summary
This Keycloak flaw lets a signed-in user register a WebAuthn credential that ignores the realm’s configured security policy. It does not expose data or allow anonymous access, but it can weaken authentication assurance by allowing non-compliant credentials into an identity system.
Executive priority
Treat this as a moderate identity-platform issue. It is not an emergency remote takeover based on the sources, but Keycloak protects authentication trust, so affected deployments using WebAuthn should be updated on the next controlled maintenance cycle.
Technical view
During WebAuthn credential registration, Keycloak relies on client-side JavaScript policy handling, while server-side processAction() fails to validate new credential parameters against realm WebAuthn policies. The CVSS 3.1 score is 4.3, with low complexity, required privileges, and low integrity impact.
Likely exposure
Exposure is limited to Red Hat build of Keycloak 26.4 and 26.6 packages listed as affected, including rhel9, rhel9-operator, and operator-bundle builds. Systems not using WebAuthn registration or not on affected Red Hat builds appear less exposed based on available sources.
Exploitation context
The sources do not report active exploitation, and the CVE is not listed as KEV. Abuse requires an authenticated user and affects credential policy integrity, not confidentiality or availability. Public sources provided do not include exploit code or weaponized details.
Researcher notes
The key weakness is CWE-603: client-side policy enforcement not matched by server-side validation. Useful validation focuses on whether server-side registration rejects credentials whose parameters conflict with configured WebAuthn policy. Evidence is Red Hat-specific; broader upstream impact is not established in the provided bundle.
Mitigation direction
Review the Red Hat CVE page and linked RHSA advisories for fixed package guidance.
Update affected Red Hat build of Keycloak 26.4 or 26.6 packages to vendor-supported unaffected builds.
Confirm WebAuthn realm policies remain configured as intended after updating.
Temporarily restrict who can register WebAuthn credentials if patching is delayed.
Validation and detection
Inventory Keycloak deployments and package versions against the affected Red Hat build entries.
Check whether WebAuthn credential registration is enabled for affected realms.
Review registered WebAuthn credentials for policy compliance where administrative requirements are strict.
Verify updates using Red Hat advisory package status, not only application version labels.
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-603: 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.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-603 · source CWE mapping
Use of Client-Side Authentication
Use of Client-Side Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.