CVE-2026-3190
Redhat Build Of Keycloak
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2026-3190 is a medium-severity Improper Handling of Insufficient Permissions or Privileges (CWE-280) vulnerability in Redhat Build Of Keycloak. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Information Repositories (T1213); 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 AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-16309
Vulnerability Data
A flaw was found in Keycloak. The User-Managed Access (UMA) 2.0 Protection API endpoint for permission tickets fails to enforce the `uma_protection` role check. This allows any authenticated user with a token issued for a resource server client, even without…
more
the `uma_protection` role, to enumerate all permission tickets in the system. This vulnerability partial leads to information disclosure.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Missing authorization check enables unauthorized enumeration of permission tickets (data repository access).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces the uma_protection role requirement on the UMA Protection API endpoint before returning permission tickets.
Ensures the resource-server client token is granted only the minimal privileges needed, blocking access when the required role is absent.
Requires the system to base access decisions on verified security attributes (roles) rather than accepting any authenticated token.
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.
Defining, enforcing and reviewing access permissions with least privilege directly prevents code paths that mishandle insufficient privileges.
Runtime monitoring of software and data surfaces adverse events triggered by unhandled permission failures.
Generating logs of permission-related events enables detection and analysis of improper handling.
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 detect missing or incorrect privilege handling.
Defines access-control policy that should prevent insufficient-privilege situations.
Specifies how access rights are granted, reviewed and revoked, directly addressing privilege handling.
Requires explicit management of privileged access rights, reducing the chance of missing privilege checks.
Secure-SDLC practices include privilege checks during design and coding.
Secure-coding standards require proper permission checks before resource access.
Hardening callouts derived
Configuration rules from DISA STIG baselines that reduce the attack surface for weaknesses of the type cited by this CVE. Derived transitively via CVE→CWE→STIG over `controls_xwalks` (authoritative rows only).
Oracle Linux 8 (1 rule)
- V-248548 OL 8 must use a Linux Security Module configured to enforce limits on system services. via CWE-280