Skip to main content
VulnerabilityPublished

CVE-2026-92856: Missing Authorization

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-92856· Medium 4.9

Not known to be exploited · CVSS 4.9 Medium.

Data as of 6 Nov 2026, 07:21 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.14.9
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Build of Keycloakkeycloak/rhbk-openshift-rhel9Affected–Fixed in–
Red Hat Build of Keycloakkeycloak-servicesAffected–Fixed in–
Red Hat Build of Keycloakrhbk/keycloak-rhel9Affected–Fixed in–
Red Hat Single Sign-On 7keycloak-servicesAffected–Fixed in–

AI-suggested

Currently, no effective mitigation or patch meets Red Hat's criteria for ease of use, deployment, applicability, or stability. Users should monitor Red Hat advisories for updates. Until a fix is available, organizations should carefully evaluate their SAML brokering configurations and the use of ProxyRestriction conditions from upstream providers to minimize exposure.

Description

A vulnerability in the SAML brokering component of Keycloak allows users to bypass ProxyRestriction constraints set by upstream identity providers. This flaw enables unauthorized login to downstream services despite explicit restrictions on session sharing. Exploitation requires a specific SAML brokering configuration and the presence of ProxyRestriction conditions from a trusted upstream provider. The issue stems from Keycloak's failure to enforce these ProxyRestriction constraints during the brokering process.

References

Community reviews

Loading reviews…