Red Hat build of Keycloak: Type Confusion (CVE-2026-15572)
Published Last modified Sources: OSV, CVE.org, BSI
What is affected, what to do
A flaw was found in Keycloak's Dynamic Client Registration (DCR) security policy management. The "Allowed Protocol Mapper Types" policy, which restricts which types of data mappers a client can use, fails to re-validate the mapper type during a client update if the mapper's configuration remains unchanged.
Update Red Hat build of Keycloak 26.4 to version 26.4.14-1, Red Hat build of Keycloak 26.4 to version 26.4-22, Red Hat build of Keycloak 26.6 to version 26.6.5-1.
- Affected
- Red Hat build of Keycloak 26.4
lt *..26.4.14-1 - Red Hat build of Keycloak 26.4
lt *..26.4-22 - Red Hat build of Keycloak 26.6
lt *..26.6.5-1 - Red Hat build of Keycloak 26.6
lt *..26.6-11
- Red Hat build of Keycloak 26.4
- Fixed in
- Red Hat build of Keycloak 26.4
26.4.14-1 - Red Hat build of Keycloak 26.4
26.4-22 - Red Hat build of Keycloak 26.6
26.6.5-1 - Red Hat build of Keycloak 26.6
26.6-11
- Red Hat build of Keycloak 26.4
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
8.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
8.8
CVSS v3
Severity High on the scale from 0 to 10.
Source: OSV, CVE.org, BSI
0.7 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 51.3
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 87.19 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 8.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 8.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.7 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 51.3
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 5 August 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-843
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
A flaw was found in Keycloak's Dynamic Client Registration (DCR) security policy management. The "Allowed Protocol Mapper Types" policy, which restricts which types of data mappers a client can use, fails to re-validate the mapper type during a client update if the mapper's configuration remains unchanged. An attacker with client registration privileges can exploit this by first registering an allowed mapper type with a malicious configuration and then swapping it for a restricted, high-privilege mapper type (such as one that hardcodes administrative roles). This allows the attacker to gain full administrative access to the Keycloak realm.
Source: OSV (Open Source Vulnerabilities), cvelistv5, NVD (NIST), BSI WID Portal, BSI CSAF
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Red Hat | Red Hat build of Keycloak 26.4 |
|
|
| Red Hat | Red Hat build of Keycloak 26.4.14 |
|
|
| Red Hat | Red Hat build of Keycloak 26.6 |
|
|
| Red Hat | Red Hat build of Keycloak 26.6.5 |
|
|
| redhat | build_of_keycloak |
|
|
| Open Source | Keycloak Red Hat build of Keycloa |
|
|
Distribution and container packages (2)
Downstream packages (e.g. Bitnami, Debian, Ubuntu, Red Hat). Versions refer to the distribution, not the vendor.
| Affected versions | Fixed in | ||
|---|---|---|---|
| bitnami | keycloak |
|
|
Vendors and products
Weakness classes (CWE)
CWE-843Access of Resource Using Incompatible Type ('Type Confusion')
Base
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
Entry at MITRE CWE-843
References & sources
- access.redhat.comRHSA-2026:50846web, Vendor advisory, x_refsource_REDHAT
- access.redhat.comRHSA-2026:50847web, Vendor advisory, x_refsource_REDHAT
- access.redhat.comRHSA-2026:50848web, Vendor advisory, x_refsource_REDHAT
- access.redhat.comRHSA-2026:50849web, Vendor advisory, x_refsource_REDHAT
- access.redhat.comsecurity/cve/CVE-2026-15572web, Vulnerability database, x_refsource_REDHAT
- bugzilla.redhat.comRHBZ#2499592web, Issue tracking, x_refsource_REDHAT
- NVD (NIST)vuln/detail/CVE-2026-15572web
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Initial analysis by NVDNVD
Newly listed as affected:- Red Hat Build of Keycloak (26.4 – before 26.4.14; 26.6 – before 26.6.5)
Show 7 original changes
Individual changes of this event as published by NVD Type Action Before After Product configuration added —OR *cpe:2.3:a:redhat:build_of_keycloak:*:*:*:*:*:*:*:* versions from (including) 26.4 up to (excluding) 26.4.14 *cpe:2.3:a:redhat:build_of_keycloak:*:*:*:*:*:*:*:* versions from (including) 26.6 up to (excluding) 26.6.5Reference type added —Red Hat, Inc.: https://access.redhat.com/errata/RHSA-2026:50846 Types: Vendor AdvisoryReference type added —Red Hat, Inc.: https://access.redhat.com/errata/RHSA-2026:50847 Types: Vendor AdvisoryReference type added —Red Hat, Inc.: https://access.redhat.com/errata/RHSA-2026:50848 Types: Vendor AdvisoryReference type added —Red Hat, Inc.: https://access.redhat.com/errata/RHSA-2026:50849 Types: Vendor AdvisoryReference type added —Red Hat, Inc.: https://access.redhat.com/security/cve/CVE-2026-15572 Types: Vendor AdvisoryReference type added —Red Hat, Inc.: https://bugzilla.redhat.com/show_bug.cgi?id=2499592 Types: Issue Tracking, Vendor AdvisorySource identifier: nvd@nist.gov
Record modifiedRed Hat
1 individual change: Affected versions (publisher)
Show the original change
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) changed Red Hat build of Keycloak 26.4, Red Hat build of Keycloak 26.4, Red Hat build of Keycloak 26.4 (+5)Red Hat build of Keycloak 26.4, Red Hat build of Keycloak 26.4, Red Hat build of Keycloak 26.4 (+5)Source identifier: secalert@redhat.com
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-15572","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-05T18:11:15.009019Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedRed Hat
CVSS V3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness type: CWE-843
Description added or changed
Show 6 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Red Hat Build of KeycloakDescription added —A flaw was found in Keycloak's Dynamic Client Registration (DCR) security policy management. The "Allowed Protocol Mapper Types" policy, which restricts which types of data mappers a client can use, fails to re-validate the mapper type during a client update if the mapper's configuration remains unchanged. An attacker with client registration privileges can exploit this by first registering an allowed mapper type with a malicious configuration and then swapping it for a restricted, high-privilege mapper type (such as one that hardcodes administrative roles). This allows the attacker to gain full administrative access to the Keycloak realm.CVSS added —AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HWeakness type (CWE) added —CWE-843Reference added —https://access.redhat.com/security/cve/CVE-2026-15572Reference added —https://bugzilla.redhat.com/show_bug.cgi?id=2499592Source identifier: secalert@redhat.com
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-15572"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-15572.svg?lang=en" alt="CVE-2026-15572 – NEOSEC Intel" height="20"></a>