Read the docs

Keycloak required actions can be bypassed via kc_action parameter

Priority LOW 24CWE-287Published · 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-287.

Summary

Red Hat Build of Keycloak is affected. Incorrect handling of application-initiated actions in the required action provider mechanism (CWE-287) lets Keycloak skip mandatory challenges when the kc_action parameter names a required action already assigned to the user. An authenticated user with low privileges can obtain an authorization code without completing profile updates or agreeing to terms, bypassing administrative requirements.

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

Description from the CNA

A flaw was found in the required action provider mechanism of Keycloak. The issue occurs when an authorization request includes the kc_action query parameter set to a mandatory action already assigned to the user, such as profile verification or terms and conditions. Due to incorrect handling of application-initiated actions, Keycloak may skip these mandatory challenges and issue an authorization code. This can allow a user to bypass administrative requirements and gain access to the application without completing necessary profile updates or agreeing to terms.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00195 9th 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 states that no fix plan is available for it. Red Hat Single Sign-On 7 is 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-30 Threatist record created from CVE-2026-118959
  2. 2026-10-30 Alias added: GHSA-74cm-5prx-222c
  3. 2026-10-31 Priority changed: MEDIUM → LOW
  4. 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