Is CVE-2026-17059 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-17059 being exploited in the wild.

How severe is CVE-2026-17059?

Medium severity, with a CVSS score of 6.5, published 24 July 2026.

Which products and versions are affected?

Keycloak unspecified; Red Hat build of Keycloak unspecified.

Is there a fix for CVE-2026-17059?

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-17059 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-17059?

Check whether you run Keycloak or Red Hat build of Keycloak at an affected version. 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.

CVE-2026-17059: Keycloak keycloak-services authorization bypass in role-users endpoint

CVE-2026-17059 · Severity: medium · CVSS 6.5 · Published 2026-07-24

A security flaw in Keycloak, a popular identity and access management tool, allows certain administrative users to view private information they are not authorized to see. Specifically, an administrator with restricted permissions can bypass security filters to access the names and email addresses of users by viewing role membership lists. This could lead to the unauthorized exposure of sensitive employee or customer data within the organization.

Technologies: Keycloak, Red Hat build of Keycloak. Vendors: Keycloak, Red Hat.

Quick answers

Is CVE-2026-17059 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-17059 being exploited in the wild.
How severe is CVE-2026-17059?: Medium severity, with a CVSS score of 6.5, published 24 July 2026.
Which products and versions are affected?: Keycloak unspecified; Red Hat build of Keycloak unspecified.
Is there a fix for CVE-2026-17059?: 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-17059 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-17059?: Check whether you run Keycloak or Red Hat build of Keycloak at an affected version. 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

An authorization bypass vulnerability exists in the 'role-users' REST API endpoint within the keycloak-services library. The root cause is located in the RoleResource.getRoleUserMembers method, which verifies if a caller has permission to view a specific role but fails to apply per-user view filters to the resulting list. An authenticated attacker with restricted administrative privileges (such as 'query-users' or 'view-realm') can exploit this by requesting the list of users assigned to a role via the GET /admin/realms/{realm}/roles/{role-name}/users endpoint. This allows the attacker to perform unauthorized enumeration of User PII, including usernames, email addresses, and full names, bypassing intended access restrictions.

Affected products

Red Hat Red Hat Build of Keycloak unspecified
Keycloak keycloak-services unspecified

Timeline

2026-07-24: disclosed: CVE published and reported by Red Hat

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.