Quick answers
- Is CVE-2026-92855 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92855 being exploited in the wild.
- How severe is CVE-2026-92855?
- High severity, with a CVSS score of 7.4, published 5 November 2026.
- Which products and versions are affected?
- Red Hat Keycloak.
- Is there a fix for CVE-2026-92855?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-92855 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-92855?
- Check whether you run Red Hat Keycloak. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The SAML identity broker component in Keycloak does not enforce proof of key possession when processing holder-of-key assertions, allowing assertion replay attacks. An attacker with network access to intercept a valid signed SAML assertion issued for a victim can reuse that assertion to gain unauthorized access and assume the victim's identity. This is an improper authentication vulnerability (CWE-287) that requires only the ability to observe or intercept SAML traffic.
Affected products
- Red Hat Keycloak
Timeline
- 2026-11-05: disclosed