Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-w3p3-7cjg-vgfw

Keycloak allows unauthorized access to resources via uma permission ticket bypass

CVSS 4.6 MediumEPSS 0.0029 · 22nd percentile

Published by the GitHub Advisory Database at 29 Oct 2026, 16:37 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.keycloak:keycloak-servicesMaven<26.6.426.6.4
Identifiers
GHSA-w3p3-7cjg-vgfw · BIT-keycloak-2026-9799 · CVE-2026-9799
Weakness (CWE)
CWE-639
Tags
Published
29 Oct 2026
Updated
29 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Keycloak (Maven package org.keycloak:keycloak-services) versions before 26.6.4 are affected. An authenticated user who holds a UMA permission ticket for one resource can bypass per-resource access control and gain access to other resources of the same type within the same resource server, which may lead to unauthorized information disclosure or modification. This requires the resource server to use PERMISSIVE policy enforcement mode and typed resources with ownerManagedAccess enabled that have no explicit protecting policy. Upgrade to Keycloak 26.6.4 or later.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.6 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.0029, the 22nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.