Skip to content
Fencer Intel
low 3.1

CVE-2025-12150 json

Org.keycloak/keycloak-services: webauthn attestation statement verification bypass

published 8mo ago modified 2mo ago also BIT-keycloak-2025-12150 , EUVD-2025-208135 , GHSA-7g5x-9c4v-4w5r

cvss
3.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.keycloak:keycloak-services 26.4.4
  • bitnami keycloak 26.4.4
  • Keycloak keycloak 26.4.4
  • Red Hat Red Hat build of Keycloak 26.2 26.2-12, 26.2.11-1
  • Red Hat Red Hat build of Keycloak 26.4 26.4-3, 26.4.4-1

Is CVE-2025-12150 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-12150 updated cvss 3.1

org.keycloak/keycloak-services: WebAuthn Attestation Statement Verification Bypass

  • Red Hat build of Keycloak 26.2 rhbk/keycloak-rhel9 26.2-12, rhbk/keycloak-rhel9-operator 26.2-12, rhbk/keycloak-operator-bundle 26.2.11-1
    fixed: vendor fix RHSA-2025:22088
  • Red Hat build of Keycloak 26.2.11
    fixed: vendor fix RHSA-2025:22089
  • Red Hat build of Keycloak 26.4 rhbk/keycloak-rhel9 26.4-3, rhbk/keycloak-rhel9-operator 26.4-3, rhbk/keycloak-operator-bundle 26.4.4-1
    fixed: vendor fix RHSA-2025:21371
  • Red Hat build of Keycloak 26.4.4
    fixed: vendor fix RHSA-2025:21370

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
8mo ago

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N
GitHub 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N
NVD 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N
OSV 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-services
<26.4.4
26.4.4
bitnami keycloak
<26.4.4
26.4.4

Affected products

  • Keycloak keycloak
  • Red Hat Red Hat build of Keycloak 26.2
  • Red Hat Red Hat build of Keycloak 26.2.11
  • Red Hat Red Hat build of Keycloak 26.4
  • Red Hat Red Hat build of Keycloak 26.4.4

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.