Your RSA-2048 keys break in 2030. Find every one of them before attackers do.

CVE-2026-4636

HIGH

CVE-2026-4636 is a high-severity (CVSS 8.1) CWE-551 vulnerability in redhat build of keycloak. O3 Security detects and blocks CVE-2026-4636 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

A flaw was found in Keycloak. An authenticated user with the uma_protection role can bypass User-Managed Access (UMA) policy validation. This allows the attacker to include resource…

Published
Apr 2, 2026
Updated
Jul 15, 2026
Affected
0 pkgs
Patched
None yet
Exploits
None indexed

Description

A flaw was found in Keycloak. An authenticated user with the uma_protection role can bypass User-Managed Access (UMA) policy validation. This allows the attacker to include resource identifiers owned by other users in a policy creation request, even if the URL path specifies an attacker-owned resource. Consequently, the attacker gains unauthorized permissions to victim-owned resources, enabling them to obtain a Requesting Party Token (RPT) and access sensitive information or perform unauthorized actions.

Affected Products

1 product · 5 configurations
Application
build of keycloakredhat
4 versions
26.226.2.1526.426.4.11

Detection & mitigation playbook

Vendor / appliance
  1. Detect

    Inventory every redhat build of keycloak deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

  2. Remediation status

    No patch has shipped for CVE-2026-4636 yet — track the redhat build of keycloak advisory for a fixed release and apply the workarounds below in the meantime.

  3. Mitigate without a patch

    Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

  4. How O3 protects you

    O3 detects and blocks CVE-2026-4636 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2026-4636. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A flaw was found in Keycloak. An authenticated user with the uma_protection role can bypass User-Managed Access (UMA) policy validation. This allows the attacker to include resource identifiers owned by other users in a policy creation request, even if the URL path specifies an attacker-owned resource. Consequently, the attacker gains unauthorized permissions to victim-owned resources, enabling them to obtain a Requesting Party Token (RPT) and access sensitive information or perform unauthorized actions.
O3 Security · Runtime Protection

Is CVE-2026-4636 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2026-4636 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.