dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2026-3009

HIGH · 8.1 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability in Keycloak's IdentityBrokerService.performLogin endpoint allows authentication through disabled Identity Providers by reusing previously generated login requests. The endpoint fails to re-validate that the IdP is still enabled at login execution time, only checking at login initiation, allowing attackers with knowledge of the IdP alias to bypass administrative restrictions.

MitigationImplement server-side validation in the performLogin endpoint to verify the IdP is enabled immediately before processing the authentication request, and invalidate any pending login requests when an IdP is disabled.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of KeycloakApplication
Affected:all versions= 26.4= 26.4.10
Jboss Enterprise Application PlatformApplication
Affected:= 8.0
Jboss Enterprise Application Platform Expansion PackApplication
Affected:all versions
Single Sign OnApplication
Affected:= 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Keycloak or SSO version
    Check the product version by examining the build metadata, manifest, or running 'kc.sh --version' for Keycloak Container images, or check the RPM/package version for RH-SSO (e.g., 'rpm -q rh-sso7' or 'rpm -q jboss-eap-rhel8'). Compare this version against the affected ranges: RH Build of Keycloak (all versions, 26.4, 26.4.10), RH JBoss EAP (8.0), RH JBoss EAP Expansion Pack (all versions), RH SSO (7.0).
    Affected if The installed version matches any of the affected versions or falls within an affected version range.
  2. Confirm Identity Providers are configured
    Access the Keycloak admin console or use the admin REST API (GET /{realm}/identity-provider/instances) to list all configured identity providers. Check whether any IdP instances exist in the realm.
    Affected if One or more IdPs are configured in the Keycloak realm.
  3. Identify disabled IdP instances
    Review the IdP configuration list and check the 'enabled' attribute for each provider. In the admin console, disabled IdPs show as disabled; via API, the 'enabled' field will be set to false for disabled providers. Note the alias names of any disabled IdPs.
    Affected if Any IdP exists with the 'enabled' flag set to false.
  4. Review authentication logs for disabled IdP access attempts
    Examine Keycloak server logs (typically under $KEYCLOAK_HOME/standalone/log/ or /var/log/keycloak/) for HTTP 302 redirects or authentication flows referencing the performLogin endpoint with the alias of disabled IdPs. Search for patterns like 'performLogin' combined with disabled IdP aliases in request logs or audit trails.
    Affected if Log entries show authentication attempts (performLogin calls) using the alias of a currently disabled IdP.
  5. Check for active sessions from disabled IdPs
    Use the admin API (GET /{realm}/user-sessions) or admin console to list active user sessions. Cross-reference session details to identify any sessions authenticated through IdPs that are now disabled.
    Affected if Active user sessions exist that were established via an IdP that is currently disabled.

A system is affected if it runs an affected Keycloak/JBoss EAP/RH-SSO version, has configured IdPs, and has any disabled IdP whose alias could be replayed in authentication requests, or if authentication logs show attempts to authenticate via disabled IdPs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement server-side validation in the performLogin endpoint to verify the IdP is enabled immediately before processing the authentication request, and invalidate any pending login requests when an IdP is disabled.

Recommended fix Moderate confidence

Keycloak 26.4.11 or later / Red Hat build corresponding to 26.4.11

  1. 1. Identify the current Keycloak version in use by checking the server logs or installation directory
  2. 2. For Keycloak standalone installations: Download Keycloak 26.4.11 or later from the official Keycloak releases page (github.com/keycloak/keycloak)
  3. 3. For Red Hat middleware deployments: Apply the corresponding Red Hat Security Advisory (RHSA) for this CVE from access.redhat.com/security/updates/
  4. 4. Test the upgrade in a non-production environment first to verify the fix works correctly
  5. 5. Back up the current Keycloak database before performing the upgrade
  6. 6. Perform the upgrade following standard Keycloak migration procedures
  7. 7. Verify that disabled Identity Providers can no longer be used for authentication by attempting to use a disabled IdP's previous login request
Caveat Review Keycloak 26.4.11 release notes for any breaking changes; test thoroughly before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3009 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3009 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data