CVE-2026-15571
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:NSummary
CVE-2026-15571 is a high-severity Predictable from Observable State (CWE-341) vulnerability. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-61238
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.6.1V6.5.1V6.5.3V6.5.5
Mitigating Controls (NIST 800-53 r5) AI
Authenticator management requires generation and distribution of values that cannot be derived from observable state.
Cryptographic key establishment mandates use of unpredictable, non-observable values for keys and nonces.
Session authenticity protection requires session identifiers or tokens that resist prediction from network or timing observations.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require cryptographically secure random values instead of observable state such as time or PID.
Hardened configuration baselines can enforce use of cryptographically secure RNG sources and disable predictable state-based mechanisms.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Cryptographic controls replace predictable values with high-entropy, non-guessable material.
Security testing can detect predictability issues but does not prevent them by itself.
SDLC requirements encourage secure design but do not directly mandate removal of predictable state.
Secure coding practices explicitly forbid use of predictable state (time, PID, counters) for secrets or tokens.
Strong authentication mechanisms reduce reliance on predictable state-derived tokens or identifiers.
Accurate time sources limit one observable state vector but do not address broader predictability.