# CVE-2026-92855: Keycloak SAML broker authentication bypass in holder-of-key assertion verification

Source: https://junglewise.ai/threats/cve-2026-92855-a-flaw-was-found-in-the-saml-identity-broker-component-of  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-05. Updated: 2026-11-05  
License: CC BY 4.0 with a link back

CVE-2026-92855 · Severity: high · CVSS 7.4 · Published 2026-11-05

Keycloak is an identity and access management system used to delegate authentication to external identity providers. A flaw in its SAML broker component fails to verify that users actually possess the private key associated with holder-of-key assertions, allowing attackers who intercept a signed assertion to replay it and impersonate victims without needing their private key, bypassing authentication entirely.

Technologies: [Red Hat Keycloak](https://junglewise.ai/threats/technologies/red-hat-keycloak). Vendors: [Red Hat](https://junglewise.ai/threats/vendors/red-hat).

## 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

## References

- [https://access.redhat.com/downloads/content/package-browser/](https://access.redhat.com/downloads/content/package-browser/)
- [https://access.redhat.com/security/cve/CVE-2026-92855](https://access.redhat.com/security/cve/CVE-2026-92855)

## Related threats

- [Red Hat Keycloak missing authorization check in group reparenting](https://junglewise.ai/threats/cve-2026-116468-a-flaw-was-found-in-the-group-move-and-organization-group)
- [Keycloak privilege escalation via client authentication manipulation](https://junglewise.ai/threats/cve-2026-9797-a-flaw-was-found-in-keycloak-s-administrative-services-org)
- [Keycloak Account REST API session manipulation](https://junglewise.ai/threats/cve-2026-97367-a-flaw-was-found-in-the-keycloak-account-rest-api-where-it)
- [Keycloak token exchange lifetime bypass in Standard Token Exchange V2](https://junglewise.ai/threats/cve-2026-96460-a-flaw-was-found-in-the-token-exchange-mechanism-of-keycloak-when)
- [Keycloak SAML broker ProxyRestriction bypass](https://junglewise.ai/threats/cve-2026-92856-a-flaw-was-found-in-the-saml-brokering-component-of-keycloak-an)