Red Hat Build of Keycloak required action bypass in login consent flow
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Summary
Red Hat Build of Keycloak and Red Hat Single Sign-On are affected. An authenticated remote user who has a pending required security action, such as setting up multi-factor authentication, can send a crafted request to the consent endpoint without a valid session code and complete login, gaining access to applications without meeting the required policies.
Written by a model
Original description
A flaw was found in Keycloak. An authenticated remote user with a pending required security action, such as configuring multi-factor authentication (MFA), can bypass the mandatory action by submitting a specially crafted request to the consent endpoint without a valid session code. Keycloak incorrectly interprets the submission as a page refresh and completes the authentication process, allowing the user to access the application without fulfilling the required security policies.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133221 (Org.keycloak.authentication: pending required actions (e.g. configure_totp) can be bypassed via post to login-actions/consent without a…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133221 (entry last updated 2026-11-19):
Affected:
- Red Hat Red Hat Build of Keycloak: version range not reported
- Red Hat Red Hat Build of Keycloak: version range not reported
- Red Hat Red Hat Single Sign-On 7: version range not reported
- Red Hat Red Hat Single Sign-On 7: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133221 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133221 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2576986
- https://access.redhat.com/security/cve/CVE-2026-133221
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133221
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133221"}.Affected versions
- keycloak-services
- rhbk/keycloak-rhel9
- keycloak-services
- rh-sso7-keycloak
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Shipped in major Linux distributions
- Severity5.4/10CVSS 5.4
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 78 if added to CISA KEV
- Would score about 73 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133221 |
| Record | NVD · CVE-2026-133221 |
| Write-ups 1Establishes: Technical detail and context. | |
| Report | bugzilla.redhat.com · show_bug.cgi?id=2576986 |
| Other links 1 | |
| Link | access.redhat.com · security/cve/CVE-2026-133221 |
Related
- CVE-2026-120984Keycloak-services: keycloak-services: manage-clients to arbitrary code execution through inline javascript policy import
- CVE-2026-12977Org.wildfly.core/wildfly-server: wildfly: rbac bypass in wildfly deployment-operation handlers leads to privilege escalation
- CVE-2026-133537Org.keycloak:keycloak-services: org.keycloak:keycloak-common: uma uri suffix matching authorization bypass
- CVE-2026-133228Org.keycloak.services.resources: client minimum acr (level of authentication) is not enforced when the login starts at the credential…
- CVE-2026-125652Keycloak-services: keycloak-services: client-level mandatory pkce bypass via login-actions entry point
- CVE-2026-116468Keycloak-services: keycloak-services: delegated admin escalates to realm-admin via group move
No corrections so far. Something wrong on this page? Report an error.