Skip to main content

Keycloak CVE-2026-16442

| EUVDEUVD-2026-53395 CRITICAL
Origin Validation Error (CWE-346)
2026-08-05 redhat GHSA-vj6m-hv26-qx79
9.8
CVSS 3.1 · NVD
Share

Severity by source

Vendor (redhat) PRIMARY
HIGH
qualitative
NVD
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
9.1 CRITICAL

Network-reachable endpoint with no privileges on Keycloak yields AV:N/PR:N; account takeover gives C:H/I:H, but there is no direct availability impact so A:N (vs vendor A:H).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Red Hat
7.4 HIGH
qualitative

Primary rating from Vendor (redhat).

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

6
Analysis Updated
Aug 10, 2026 - 19:29 vuln.today
v2 (cvss_changed)
Re-analysis Queued
Aug 10, 2026 - 19:22 vuln.today
cvss_changed
Severity Changed
Aug 10, 2026 - 19:22 NVD
HIGH CRITICAL
CVSS changed
Aug 10, 2026 - 19:22 NVD
7.4 (HIGH) 9.8 (CRITICAL)
Analysis Generated
Aug 05, 2026 - 15:47 vuln.today
CVE Published
Aug 05, 2026 - 15:00 cve.org
HIGH 7.4

DescriptionNVD

A flaw was found in the SAML broker component of Keycloak, which is used to manage identity federation and user authentication. The issue occurs because the IdP-initiated Single Sign-On endpoint fails to check if a provider is restricted to account linking only. This allows an attacker with control over a linked upstream identity to bypass login restrictions and gain full access to a local user account.

AnalysisAI

Account takeover in Keycloak (Red Hat build of Keycloak, Red Hat Single Sign-On 7) arises because the IdP-initiated SAML SSO endpoint does not verify whether an upstream identity provider is restricted to account-linking-only mode. An attacker who controls a linked upstream identity can drive that endpoint to complete a full login rather than a mere link operation, seizing complete access to the corresponding local user account. Red Hat has shipped fixes; there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.19%).

Technical ContextAI

Keycloak is a widely used open-source identity and access management server that brokers external identity providers (IdPs) for federation and single sign-on. The affected code path is the SAML broker's IdP-initiated SSO endpoint, which processes unsolicited SAML responses pushed from an external IdP. Administrators can configure a broker provider so that it may only be used to link an external identity to an existing local account ('account linking only'), not to authenticate and establish a full session. The flaw is a CWE-346 origin/authorization-context validation failure: the endpoint fails to enforce that account-linking-only restriction, so a SAML assertion that should only be permitted to link is instead honored as a full authentication. Affected packages per the CPE data include red_hat_build_of_keycloak, red_hat_single_sign-on_7, and the Keycloak-derived components shipped with Red Hat Data Grid 8 and the JBoss EAP Expansion Pack.

RemediationAI

Apply the vendor-released patches: update the Red Hat build of Keycloak to 26.4 (package 26.4-22 or 26.4.14-1) or 26.6 (package 26.6-11 or 26.6.5-1), and apply the corresponding RHSA errata for the affected products (https://access.redhat.com/errata/RHSA-2026:50846, RHSA-2026:50847, RHSA-2026:50848, and RHSA-2026:50849). If immediate patching is not possible, reduce exposure by auditing all SAML broker identity providers configured as account-linking-only and temporarily disabling those providers or the IdP-initiated SSO flow for them, accepting the trade-off that users relying on those links will lose that federation path until patched; additionally restrict or firewall the SAML broker endpoint to trusted networks, and review recently created or reactivated account links for signs of abuse. Consult the Red Hat CVE page (https://access.redhat.com/security/cve/CVE-2026-16442) for the authoritative fixed builds before deploying.

CVE-2026-18963 CRITICAL POC
9.1 Aug 18

Account takeover in Red Hat Build of Keycloak allows an unauthenticated attacker to abuse the reset-credentials flow in

CVE-2026-16443 CRITICAL
9.1 Aug 05

Authentication bypass in Red Hat Build of Keycloak (and Red Hat Single Sign-On 7) lets an unauthenticated attacker forge

CVE-2026-15572 HIGH
8.8 Aug 05

Privilege escalation in Red Hat Build of Keycloak's Dynamic Client Registration (DCR) grants an attacker with low-privil

CVE-2026-93569 HIGH
8.2 Sep 18

Mismatched handling of the HTTP/1 absolute-form request authority in Red Hat build of Quarkus and other affected Red Hat

CVE-2026-9800 HIGH
8.1 Jun 25

Authorization bypass in the Keycloak Policy Enforcer allows any authenticated user to circumvent all enforced access con

CVE-2026-15573 HIGH
8.1 Aug 05

URI normalization bypass in Keycloak's Authorization Services PathMatcher allows authenticated low-privilege users to re

CVE-2026-16102 HIGH
8.1 Aug 05

Privilege escalation in Keycloak's Dynamic Client Registration (DCR) component allows attackers with standard user accou

CVE-2026-18214 HIGH
8.1 Jul 31

Token exchange in Keycloak bypasses Google Workspace domain allowlist restrictions, enabling any valid Google account ho

CVE-2026-11800 HIGH
8.1 Jun 25

Signature-verification bypass in Keycloak (and Red Hat's Keycloak-based products such as Red Hat Single Sign-On 7 and Re

CVE-2026-18215 HIGH
8.1 Jul 31

Tenant-restriction bypass in Keycloak's Microsoft identity provider integration allows attackers holding any valid Micro

CVE-2026-18967 HIGH
8.1 Aug 06

Session hijacking via SAML assertion replay in Keycloak's SAML broker component allows adjacent-network attackers to aut

CVE-2026-7504 HIGH
8.1 May 19

Open redirect in Red Hat build of Keycloak permits remote attackers to send victims to attacker-controlled hosts by abus

Vendor StatusVendor

Share

CVE-2026-16442 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy