CVE-2026-15943
Redhat Build Of Keycloak
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:NSummary
CVE-2026-15943 is a medium-severity Improper Validation of Consistency within Input (CWE-1288) vulnerability in Redhat Build Of Keycloak. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-45164
Vulnerability Data
A flaw was found in the Keycloak keycloak-services component, which handles the management of identity providers. The issue occurs when a delegated administrator updates an OIDC identity provider using a masked client secret sentinel value. Due to improper validation, Keycloak…
more
reuses the existing real secret even if security-sensitive fields like the token URL have been changed, allowing an attacker to redirect and capture the secret.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V2.2.2V4.2.3V12.3.2
Mitigating Controls (NIST 800-53 r5) AI
SI-10 requires validity checks on supplied inputs, directly stopping acceptance of internally inconsistent complex data.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require consistency validation for complex inputs.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect consistency flaws but does not prevent them at design time.
Secure development lifecycle requires input validation and consistency checks that directly address CWE-1288.
Application security requirements include validation of complex inputs and cross-field consistency.
Secure architecture principles encourage robust input handling but do not specifically mandate consistency validation.
Secure coding standards explicitly require validation of interrelated input fields to prevent CWE-1288.