# CVE-2026-118947: Keycloak authorization bypass in UMA resource registration

Source: https://junglewise.ai/threats/cve-2026-118947-a-flaw-was-found-in-the-uma-resource-registration-endpoint-of  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-30. Updated: 2026-10-30  
License: CC BY 4.0 with a link back

CVE-2026-118947 · Severity: medium · CVSS 4.3 · Published 2026-10-30

Keycloak is an open-source identity and access management platform used to control who can access corporate applications and data. A flaw in its resource authorization feature allows an authenticated user with specific permissions to modify resources they don't own, potentially exposing or altering sensitive access configurations.

Technologies: [Red Hat Keycloak](https://junglewise.ai/threats/technologies/red-hat-keycloak). Vendors: [Red Hat](https://junglewise.ai/threats/vendors/red-hat).

## Quick answers

**Is CVE-2026-118947 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-118947 being exploited in the wild.

**How severe is CVE-2026-118947?** Medium severity, with a CVSS score of 4.3, published 30 October 2026.

**Which products and versions are affected?** Red Hat Keycloak.

**Is there a fix for CVE-2026-118947?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-118947 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-118947?** Check whether you run Red Hat Keycloak. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is an insecure direct object reference (IDOR) in the UMA resource registration endpoint, caused by a missing ownership check. An authenticated attacker with the uma_protection role can update resources they do not own by providing a target resource ID in the request, allowing modification of resource names, URIs, and scopes. The attack requires valid credentials and knowledge of the target resource ID.

## Affected products

- Red Hat Keycloak

## Timeline

- 2026-10-30: disclosed

## References

- [https://access.redhat.com/downloads/content/package-browser/](https://access.redhat.com/downloads/content/package-browser/)
- [https://access.redhat.com/security/cve/CVE-2026-118947](https://access.redhat.com/security/cve/CVE-2026-118947)

## Related threats

- [Red Hat Keycloak missing authorization check in group reparenting](https://junglewise.ai/threats/cve-2026-116468-a-flaw-was-found-in-the-group-move-and-organization-group)
- [Keycloak privilege escalation via client authentication manipulation](https://junglewise.ai/threats/cve-2026-9797-a-flaw-was-found-in-keycloak-s-administrative-services-org)
- [Keycloak Account REST API session manipulation](https://junglewise.ai/threats/cve-2026-97367-a-flaw-was-found-in-the-keycloak-account-rest-api-where-it)
- [Keycloak token exchange lifetime bypass in Standard Token Exchange V2](https://junglewise.ai/threats/cve-2026-96460-a-flaw-was-found-in-the-token-exchange-mechanism-of-keycloak-when)
- [Keycloak SAML broker ProxyRestriction bypass](https://junglewise.ai/threats/cve-2026-92856-a-flaw-was-found-in-the-saml-brokering-component-of-keycloak-an)