# CVE-2026-3009: keycloak — Fixed in 26.4.1 📦 Bitnami Not in CISA KEV # CVE-2026-3009 — keycloak CVE-2026-3009 is a CWE-863 vulnerability in keycloak. A fix is available for keycloak — see the affected versions and patch details below. Org.keycloak/keycloak-services: improper enforcement of disabled identity provider in identitybrokerservice (authentication bypass) Also known as[GHSA-m297-3jv9-m927](/vulnerability/GHSA-m297-3jv9-m927) Published Aug 25, 2026 Updated Sep 10, 2026 Affected 1 pkg Patched 1 / 1 Exploits None indexed Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - A successful exploit gives an attacker total control of the affected component, not partial access. - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2026-3009. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.4%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk 0.00%0.32%0.65%0.97%0.0%0.4%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## Real-World Exposure 1 pkg affected 📦`keycloak` Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems. ## Description A security flaw in the IdentityBrokerService.performLogin endpoint of Keycloak allows authentication to proceed using an Identity Provider (IdP) even after it has been disabled by an administrator. An attacker who knows the IdP alias can reuse a previously generated login request to bypass the administrative restriction. This undermines access control enforcement and may allow unauthorized authentication through a disabled external provider. ## Affected Packages 1 total 1 fixed Ecosystem Package Vulnerable range Fix 📦Bitnami `keycloak` ≥ 26.4.0&&< 26.4.1 26.4.1 ## Affected Products 4 products · 6 configurations Application `build of keycloak`redhat 2 versions 26.426.4.10 Application `jboss enterprise application platform`redhat 1 version 8.0 Application `jboss enterprise application platform expansion pack`redhat all Application `single sign-on`redhat 1 version 7.0 ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keycloak, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update keycloak to 26.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-3009 is resolved across your whole dependency graph. 3. ### Workarounds Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. ## Fixing This On Your OS If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project. Red HatImportant The security impact of this vulnerability is considered High because it allows bypassing an explicit administrative security control. Even though user interaction is required, an attacker can authenticate using an Identity Provider that administrators intentionally disabled. This weakens identity governance controls… Workaround published by Red Hat > Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Source: [Red Hat security advisory for CVE-2026-3009](https://access.redhat.com/security/cve/cve-2026-3009) (CC BY 4.0) Product Fixed in Advisory Red Hat build of Keycloak 26.4 `rhbk/keycloak-operator-bundle:26.4.10-1` [RHSA-2026:3948](https://access.redhat.com/errata/RHSA-2026:3948) Red Hat build of Keycloak 26.4.10 `rhbk/keycloak-rhel9` [RHSA-2026:3947](https://access.redhat.com/errata/RHSA-2026:3947) ## Frequently Asked Questions A security flaw in the IdentityBrokerService.performLogin endpoint of Keycloak allows authentication to proceed using an Identity Provider (IdP) even after it has been disabled by an administrator. An attacker who knows the IdP alias can reuse a previously generated login request to bypass the administrative restriction. This undermines access control enforcement and may allow unauthorized authentication through a disabled external provider. O3 Security · Impact-Aware SCA ### Is CVE-2026-3009 in your dependencies? Find it across Bitnami, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)