Red Hat Keycloak WebAuthn Attestation Statement Verification state issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Red Hat Keycloak. It has been rated as critical. This impacts an unknown function of the component WebAuthn Attestation Statement Verification. This manipulation causes state issue. This vulnerability is tracked as CVE-2025-12150. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Red Hat Keycloak (version unknown). It has been declared as critical. Affected by this vulnerability is an unknown function of the component WebAuthn Attestation Statement Verification. The manipulation with an unknown input leads to a state issue vulnerability. The CWE definition for the vulnerability is CWE-371. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at bugzilla.redhat.com. This vulnerability is known as CVE-2025-12150. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/05/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-2606). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Open Source Keycloak
Product
Vendor
Name
License
Website
- Vendor: https://www.redhat.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 3.1
NVD Vector: 🔒
CNA Base Score: 3.1
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: State issueCWE: CWE-371
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/31/2025 Advisory disclosed10/31/2025 VulDB entry created
03/05/2026 VulDB entry last update
Sources
Vendor: redhat.comAdvisory: bugzilla.redhat.com
Status: Confirmed
CVE: CVE-2025-12150 (🔒)
GCVE (CVE): GCVE-0-2025-12150
GCVE (VulDB): GCVE-100-330757
CERT Bund: WID-SEC-2025-2606 - Keycloak: Mehrere Schwachstellen
Entry
Created: 10/31/2025 08:18Updated: 03/05/2026 03:58
Changes: 10/31/2025 08:18 (48), 11/14/2025 12:53 (7), 03/05/2026 03:58 (21)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.