# CVE-2026-133221: A flaw was found in Keycloak.


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-vp2g-xwpj-h5g5

## What is CVE-2026-133221?

CVE-2026-133221 is a medium-severity vulnerability in org.keycloak.authentication, published on 19 Nov 2026. 

### Official 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.

Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow)

## Which versions are affected by CVE-2026-133221?

It affects 1 product.


Products: Redhat Build Keycloak.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:redhat:build_keycloak:*:*:*:*:*:*:*:*`

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Red Hat | red_hat_single_sign_on:7 | end of life | `rh-sso7-keycloak`, `rh-sso7-keycloak-server` |  |

## How do I fix CVE-2026-133221?

No fix has been published for CVE-2026-133221 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-133221 being exploited?

There is no known exploitation of CVE-2026-133221 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-133221 and fix it if it is affected.

What it is: CVE-2026-133221 is a medium-severity vulnerability in org.keycloak.authentication, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133221 in the wild and no public exploit code.

Affected product: org.keycloak.authentication. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-133221/ (Markdown: https://insights.sbomify.com/CVE-2026-133221/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-133221
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-133221
- OSV: https://osv.dev/vulnerability/CVE-2026-133221

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-133221/
Summaries are generated and may contain mistakes; the official description above is the record.
