ReviewHigh

CVE-2026-15571

Red Hat Red Hat build of Keycloak 26.6, Red Hat build of Keycloak 26.6.6, Red Hat Data Grid 8

A flaw was found in the legacy client-initiated account-linking endpoint of Keycloak, a widely used open-source identity and access management solution. The mechanism used to protect the account-linking process from unauthorized requests relies on a hash that can be predicted by a malicious OIDC client. By tricking a user into authenticating, an attacker-controlled client can forge a valid linking URL to connect the victim's account to an attacker's external identity. This results in a full account takeover, allowing the attacker to log in as the victim.

CVSS
7.3
EPSS
0.33%
25.5% percentile
CISA KEV
Not listed
Published
2026.08.19
PRIORITY ASSESSMENT

Review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.33%
Technical severityCVSS 7.3

Vulnerability overview

A flaw was found in the legacy client-initiated account-linking endpoint of Keycloak, a widely used open-source identity and access management solution. The mechanism used to protect the account-linking process from unauthorized requests relies on a hash that can be predicted by a malicious OIDC client. By tricking a user into authenticating, an attacker-controlled client can forge a valid linking URL to connect the victim's account to an attacker's external identity. This results in a full account takeover, allowing the attacker to log in as the victim.

Affected product and versions

Product
Red Hat Red Hat build of Keycloak 26.6, Red Hat build of Keycloak 26.6.6, Red Hat Data Grid 8
Affected versions
See the vendor advisory and NVD configuration data
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Red Hat Red Hat build of Keycloak 26.6, Red Hat build of Keycloak 26.6.6, Red Hat Data Grid 8 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
CWE
CWE-341