# CVE-2026-109082: Keycloak CIBA authorization bypass in keycloak-services

Source: https://junglewise.ai/threats/cve-2026-109082-a-flaw-was-found-in-the-client-initiated-backchannel  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-12. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-109082 · Severity: medium · CVSS 6.8 · Published 2026-10-12

Keycloak is an identity management system that handles user authentication and access control for enterprise applications. A flaw in its Client-Initiated Backchannel Authentication (CIBA) feature allows attackers to bypass security controls and trick users into granting unauthorized access to their accounts. An attacker could gain full access to a victim's account without needing the client application's secret credentials.

Technologies: [Keycloak](https://junglewise.ai/threats/technologies/keycloak). Vendors: [Keycloak](https://junglewise.ai/threats/vendors/keycloak).

## Quick answers

**Is CVE-2026-109082 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-109082 being exploited in the wild.

**How severe is CVE-2026-109082?** Medium severity, with a CVSS score of 6.8, published 12 October 2026.

**Which products and versions are affected?** Keycloak Keycloak.

**Is there a fix for CVE-2026-109082?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-109082 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-109082?** Check whether you run Keycloak. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is an improper authentication flaw (CWE-287) in the keycloak-services component's CIBA implementation. Keycloak fails to enforce the confidential-only client requirement, allowing public clients to initiate the CIBA flow. An attacker must trick a user into approving a push notification on their authentication device, but successful exploitation grants the attacker a full user access token.

## Affected products

- Keycloak Keycloak

## Timeline

- 2026-10-12: disclosed

## References

- [https://access.redhat.com/downloads/content/package-browser/](https://access.redhat.com/downloads/content/package-browser/)
- [https://access.redhat.com/security/cve/CVE-2026-109082](https://access.redhat.com/security/cve/CVE-2026-109082)

## Related threats

- [Keycloak login-failure storage synchronization error in MySQL/MariaDB](https://junglewise.ai/threats/cve-2026-112201-a-flaw-was-found-in-the-login-failure-storage-component-of)
- [Keycloak PKCE bypass in login after password reset](https://junglewise.ai/threats/cve-2026-125652-a-flaw-was-found-in-the-keycloak-services-component-of-keycloak)
- [Keycloak server arbitrary code execution in client authorization](https://junglewise.ai/threats/cve-2026-120984-a-flaw-was-found-in-the-keycloak-server-s-client-management)
- [Keycloak token sanitization bypass in protocol mapper](https://junglewise.ai/threats/cve-2026-97848-a-flaw-was-found-in-the-token-sanitization-logic-of-keycloak-an)
- [Keycloak Dynamic Client Registration privilege escalation](https://junglewise.ai/threats/cve-2026-96547-a-flaw-was-found-in-the-dynamic-client-registration-component-of)