Cyber Resilience

CVE-2026-9800

Redhat Build Of Keycloak 26.4 – 26.4.13

Published
25 June 2026
Modified
06 August 2026
Patch / advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0036 29th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2026-9800 is a high-severity Comparison Using Wrong Factors (CWE-1025) vulnerability in Redhat Build Of Keycloak. Its CVSS base score is 8.1 (High).

Operationally, ranked at the 29th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A flaw was found in Keycloak Policy Enforcer. This vulnerability allows any authenticated user to bypass all authorization policies, including role, scope, and User-Managed Access (UMA) permission checks. By including the configured access-denied page path within a request URL, either…

more

as a path segment or a query parameter, an attacker can gain unauthorized access to protected resources.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-4634Same product: Redhat Build Of Keycloak
CVE-2026-37978Same product: Redhat Build Of Keycloak
CVE-2026-7571Same product: Redhat Build Of Keycloak
CVE-2025-7784Same product: Redhat Build Of Keycloak
CVE-2026-7500Same product: Redhat Build Of Keycloak
CVE-2026-9792Same product: Redhat Build Of Keycloak
CVE-2026-4628Same product: Redhat Build Of Keycloak
CVE-2026-9086Same product: Redhat Build Of Keycloak
CVE-2026-11800Same product: Redhat Build Of Keycloak
CVE-2026-12388Same product: Redhat Build Of Keycloak

Affected Assets

redhat
build of keycloak
26.4 — 26.4.13 · 26.6 — 26.6.4

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover incorrect comparison logic after implementation but does not stop the flaw from being written.

Requiring a documented development process and tools can embed standards that reduce introduction of erroneous comparison factors.

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.

PR.PS-06 mostly match
prevents

Secure SDLC activities such as code review and logic testing directly prevent incorrect comparison factors in code.

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.

finds

Security testing can detect incorrect comparison results during development and acceptance.

prevents

Secure development lifecycle includes requirements and reviews that can catch incorrect comparison logic.

prevents

Application security requirements can specify correct comparison criteria and validation rules.

prevents

Secure coding standards directly address proper comparison logic and factor selection.

References