Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-q35r-vvhv-vx5h

Keycloak: Missing Role Enforcement on UMA 2.0 Permission Ticket Endpoint Leads to Information Disclosure

CVSS 4.3 MediumEPSS 0.0032 · 25th percentile

Published by the GitHub Advisory Database at 26 Mar 2026, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.keycloak:keycloak-server-spi-privateMaven<26.5.626.5.6
org.keycloak:keycloak-servicesMaven<26.5.626.5.6
org.keycloak:keycloak-model-jpaMaven<26.5.626.5.6
Identifiers
GHSA-q35r-vvhv-vx5h · CVE-2026-3190
Weakness (CWE)
CWE-280
Tags
Published
26 Mar 2026
Updated
2 Apr 2026

Machine-written summary

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

Keycloak versions before 26.5.6 (packages keycloak-server-spi-private, keycloak-services, and keycloak-model-jpa) fail to enforce the uma_protection role check on the UMA 2.0 Protection API endpoint for permission tickets. An authenticated user holding a token issued for a resource server client, even without the uma_protection role, can list permission tickets across the system, which discloses information. Upgrade to version 26.5.6.

Written 3 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.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.0032, the 25th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 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.