# CVE-2026-94218: Keycloak-services: keycloak-services: 2fa setup enforcement bypass via authentication session restart endpoint

> Attackers can bypass mandatory two-factor authentication setup by restarting the authentication session, allowing password-only access to protected resources.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-rm49-qjx7-5qm5

## What is CVE-2026-94218?

CVE-2026-94218 is a low-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the authentication session management of Keycloak, an identity and access management solution. The issue occurs when an administrator enforces a stronger authentication flow, such as mandatory two-factor authentication (2FA) setup, through a client policy. A user can bypass this requirement by manually visiting a specific session restart web link during the login process. This action clears the internal markers that track the required security steps, allowing the user to log in with only a password and gain access without completing the mandated 2FA setup.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-94218 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94218 is a low-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-94218 in the wild and no public exploit code.

Affected product: Red Hat Build of Keycloak. 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-94218/ (Markdown: https://insights.sbomify.com/CVE-2026-94218/index.md)
```

## Sources

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

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