Read the docs

Keycloak CIBA flow accepts public clients that should be confidential

Priority LOW 32CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-287.

Summary

Keycloak's keycloak-services component does not verify that a client is authorized to use the Client-Initiated Backchannel Authentication (CIBA) flow, so public clients bypass its confidential-only requirements (CWE-287). A remote attacker can trick a user into approving a login request and gain full access to the user's account without a client secret. Red Hat Build of Keycloak is affected.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

A flaw was found in the Client-Initiated Backchannel Authentication CIBA implementation within the keycloak-services component of Keycloak. This component handles advanced authentication flows where a client initiates a login on behalf of a user. The issue occurs because Keycloak fails to verify that a client is authorized to use the CIBA flow, allowing public clients to bypass security requirements. An attacker could use this flaw to trick a user into approving a login request, eventually gaining full access to the users account without needing a client secret.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00248 16th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Red HatRed Hat Build of Keycloak——No fix listedCNA
Red HatRed Hat Build of Keycloak——No fix listedCNA
Red HatRed Hat Single Sign-On 7——Not affectedCNA
  • Red Hat Build of Keycloak VendorRed Hat Affected — Fixed in — No fix listed CNA
  • Red Hat Build of Keycloak VendorRed Hat Affected — Fixed in — No fix listed CNA
  • Red Hat Single Sign-On 7 VendorRed Hat Affected — Fixed in — Not affected CNA

CPE names CNA · 2

CPEVersionsRoleVendor
cpe:/a:redhat:build_keycloak:——Red Hat
cpe:/a:redhat:red_hat_single_sign_on:77—Red Hat
  • cpe:/a:redhat:build_keycloak: Versions — — ·Red Hat
  • cpe:/a:redhat:red_hat_single_sign_on:7 Versions 7 — ·Red Hat

Remediation

The sources list no fixed version for Red Hat Build of Keycloak, and Red Hat's plan for that product is none available. Red Hat Single Sign-On 7 is not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Build of KeycloakAffectedNo fix yet
Not affected: 1 product
  • Red Hat Single Sign-On 7

Timeline

  1. 2026-10-12 Threatist record created from CVE-2026-109082
  2. 2026-10-12 Affected versions changed · CNA
  3. 2026-10-12 Alias added: GHSA-68jh-rrf2-v9vr
  4. 2026-10-12 Affected versions changed · Red Hat
  5. 2026-10-12 CVSS score added · Red Hat
  6. 2026-10-12 Priority changed: MEDIUM → LOW
  7. 2026-10-16 CISA SSVC decision points changed

References

  • TI-2019-15875 Protection mechanism failure in Jenkins Pipeline: Groovy Plugin KEVCVSS 3.1CRITICAL 9.9
  • TI-2019-15874 Protection mechanism failure in Jenkins Script Security Plugin KEVCVSS 3.1CRITICAL 9.9
  • TI-2019-08259 Underflow in PHP-FPM can lead to RCE KEVCVSS 3.1CRITICAL 9.8
  • TI-2019-05363 Code injection in Elastic Kibana KEVCVSS 3.1CRITICAL 10.0
  • TI-2019-03949 Out-of-bounds write in ESXi and Horizon DaaS KEVCVSS 3.1CRITICAL 9.8
  • TI-2018-16080 A code execution vulnerability exists in the Stapler web framework used by Jenkins 2.153… KEVCVSS 3.1CRITICAL 9.8
See all 7413 →

Sources