Skip to content
Fencer Intel
high 8.8

CVE-2026-3047 json

Org.keycloak.broker.saml: keycloak saml broker: authentication bypass due to disabled saml client completing idp-initiated login

published 8mo ago modified 2mo ago also BIT-keycloak-2026-3047 , EUVD-2026-9864 , GHSA-8cr3-vpxx-92cx

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

A flaw was found in org.keycloak.broker.saml. When a disabled Security Assertion Markup Language (SAML) client is configured as an Identity Provider (IdP)-initiated broker landing target, it can still complete the login process and establish a Single Sign-On (SSO) session. This allows a remote attacker to gain unauthorized access to other enabled clients without re-authentication, effectively bypassing security restrictions.

Patch / fix

  • bitnami keycloak 26.2.1, 26.3.0, 26.4.1, 26.5.0
  • Red Hat Red Hat build of Keycloak 26.2 26.2-16, 26.2.14-1
  • Red Hat Red Hat build of Keycloak 26.4 26.4-12, 26.4.10-1

Is CVE-2026-3047 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-3047 updated cvss 8.8

org.keycloak.broker.saml: Keycloak SAML broker: Authentication bypass due to disabled SAML client completing IdP-initiated login

  • Red Hat build of Keycloak 26.2 rhbk/keycloak-rhel9 26.2-16, rhbk/keycloak-rhel9-operator 26.2-16, rhbk/keycloak-operator-bundle 26.2.14-1
    fixed: vendor fix RHSA-2026:3925
  • Red Hat build of Keycloak 26.2.14
    fixed: vendor fix RHSA-2026:3926
  • Red Hat build of Keycloak 26.4 rhbk/keycloak-rhel9 26.4-12, rhbk/keycloak-rhel9-operator 26.4-12, rhbk/keycloak-operator-bundle 26.4.10-1
    fixed: vendor fix RHSA-2026:3948
  • Red Hat build of Keycloak 26.4.10
    fixed: vendor fix RHSA-2026:3947

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
8mo ago

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA ADP 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-broker-saml
<=1.8.1.Final
 no fix listed
bitnami keycloak
>=26.2.0, <26.2.1
>=26.2.14, <26.3.0
>=26.4.0, <26.4.1
>=26.4.10, <26.5.0
26.2.1
26.3.0
26.4.1
26.5.0

Affected products

  • Red Hat Red Hat build of Keycloak 26.2
  • Red Hat Red Hat build of Keycloak 26.2.14
  • Red Hat Red Hat build of Keycloak 26.4
  • Red Hat Red Hat build of Keycloak 26.4.10

Classification

Weakness
  • CWE-305 Authentication Bypass by Primary Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.