Advisory record · GHSA-8cr3-vpxx-92cx

Keycloak SAML Broken has Authentication Bypass by Primary Weakness

CVSS 8.8 HighEPSS 0.0054 · 45th percentile

Published by the GitHub Advisory Database at 5 Mar 2026, 21:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.keycloak:keycloak-broker-samlMaven<=1.8.1.FinalNo fixed version yet
Identifiers
GHSA-8cr3-vpxx-92cx · BIT-keycloak-2026-3047 · CVE-2026-3047
Weakness (CWE)
CWE-305
Published
5 Mar 2026
Updated
26 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

keycloak-broker-saml, versions up to and including 1.8.1.Final, is affected. A remote attacker can log in via a disabled SAML client configured as an IdP-initiated broker landing target, gaining an SSO session that reaches other enabled clients without re-authentication. A fix is in release 26.5.5, so upgrade to that or later.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.8 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.0054, the 45th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.