CVE-2026-2575
Redhat Build Of Keycloak 26.4 – 26.4.10
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LSummary
CVE-2026-2575 is a medium-severity Data Amplification (CWE-409) vulnerability in Redhat Build Of Keycloak. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 40th 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 SC-5 (Denial-of-service Protection) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-12766
Vulnerability Data
A flaw was found in Keycloak. An unauthenticated remote attacker can trigger an application level Denial of Service (DoS) by sending a highly compressed SAMLRequest through the SAML Redirect Binding. The server fails to enforce size limits during DEFLATE decompression,…
more
leading to an OutOfMemoryError (OOM) and subsequent process termination. This vulnerability allows an attacker to disrupt the availability of the service.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Directly enables application-layer DoS via exploitation of decompression flaw causing OOM/crash (T1499.004).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation of SAMLRequest size and decompression bounds before processing, preventing the unbounded DEFLATE expansion that triggers OOM.
Mandates mechanisms to protect against resource-exhaustion DoS attacks exactly matching the compressed SAMLRequest vector described in the CVE.
Enables monitoring of memory usage and anomalous SAML traffic patterns that would indicate an in-progress decompression-based DoS attempt.
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-development practices include input-validation and resource-limit checks that prevent improper handling of compressed data.
Runtime monitoring of compute resources can detect exhaustion caused by decompression bombs.
Capacity planning and monitoring directly limits the availability impact of data-amplification attacks.
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.
Security testing can uncover decompression-bomb vulnerabilities before release.
Redundancy helps availability but does not address the root cause of the weakness.
Monitoring can detect anomalous resource usage but does not prevent the weakness.
Secure development lifecycle includes input validation and resource-limit checks that mitigate data-amplification attacks.
Application security requirements can mandate limits on decompression size and ratio.
Secure architecture principles encourage defensive design against resource-exhaustion threats.