CVE-2026-16443: Red Hat build of Keycloak 26.4 · Improper Verification of Cryptographic Signature
Affects Red Hat build of Keycloak 26.4Source CVE Database V5
Not known to be exploited · CVSS 7.4 High.
Data as of 3 Nov 2026, 10:57 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat build of Keycloak 26.4 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.4 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.4.14 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.6 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.6 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.6.5 | Affected– | Fixed in– |
AI-suggested
According to the Red Hat advisory, no mitigation currently meets the criteria for ease of use, applicability, or stability. Users should monitor Red Hat's official advisories for updates or patches addressing this vulnerability. The advisory mentions a security update for Red Hat build of Keycloak 26.4.14 that includes multiple fixes; users should verify if this update addresses CVE-2026-16443 and apply it accordingly. Until a fix is confirmed, consider restricting or reviewing SAML metadata imports to ensure usage attributes are properly specified or avoid importing metadata lacking these attributes if possible.
Description
A flaw was found in the SAML metadata import functionality of the keycloak-services component, which is the core engine for identity brokering in Red Hat Build of Keycloak. When importing identity provider metadata that lacks specific usage attributes for keys, the system incorrectly disables signature validation for SAML responses even if a signing certificate is provided. This issue allows an unauthenticated attacker to forge a SAML response and gain unauthorized access to a user account by knowing their external identifier.
References
- access.redhat.com/security/cve/CVE-2026-16443 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2503139 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:50846 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:50847 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:50848 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:50849 (opens in a new tab)