Read the docs

Keycloak JWT grant skips identity provider login restrictions

Priority LOW 24CWE-862Published · Updated

Key facts

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

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

Summary

Red Hat Build of Keycloak fails to apply identity provider login restrictions, such as claim filtering, in the JWT Authorization Grant flow (CWE-862). Browser logins enforce these checks for OIDC and Google identity providers, but the JWT grant skips them. An authenticated client with low privileges can obtain access tokens for a user whose identity provider claims should have blocked the login.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

Description from the CNA

A flaw was found in the JWT Authorization Grant implementation of the keycloak-services component. When an OIDC or Google identity provider is configured with specific login restrictions, such as claim filtering, these checks are correctly applied during standard browser logins but are skipped during the JWT-based grant flow. This allows an authenticated client to obtain access tokens for a user even if their identity provider claims should have blocked the login.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00246 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
Partial

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. Red Hat's plan for Red Hat Build of Keycloak is listed as none available. Red Hat Single Sign-On 7 is listed as not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

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-29 Threatist record created from CVE-2026-117627
  2. 2026-10-29 Affected versions changed · Red Hat
  3. 2026-10-29 CVSS score added · Red Hat
  4. 2026-10-29 Alias added: GHSA-4mr3-gfq4-fhxv
  5. 2026-10-30 Priority changed: MEDIUM → LOW
  6. 2026-11-03 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