Red Hat Keycloak/Single Sign-On Session Management improper authentication

Summaryinfo

A vulnerability has been found in Red Hat Keycloak and Single Sign-On and classified as critical. This affects an unknown function of the component Session Management. Performing a manipulation results in improper authentication. This vulnerability is known as CVE-2026-94218. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Red Hat Keycloak and Single Sign-On (the affected version unknown). It has been classified as critical. This affects an unknown part of the component Session Management. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at access.redhat.com. This vulnerability is uniquely identified as CVE-2026-94218 since 09/21/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/21/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at EUVD (EUVD-2026-83846) and CERT Bund (WID-SEC-2026-3484). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

• Open Source Keycloak

Productinfo

Vendor

• Red Hat

Name

• Keycloak
• Single Sign-On

License

• open-source

Website

• Vendor: https://www.redhat.com/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion