CVE-2025-14778 is a medium-severity (CVSS 5.4) CWE-266 vulnerability in org.keycloak:keycloak-services. A fix is available for org.keycloak:keycloak-services — see the affected versions and patch details below.
Keycloak Affected by Broken Access Control Vulnerability in the UserManagedPermissionService
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-14778.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.keycloak:keycloak-services☕org.keycloak:keycloak-services☕org.keycloak:keycloak-servicesReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A flaw was found in Keycloak. A significant Broken Access Control vulnerability exists in the UserManagedPermissionService (UMA Protection API). When updating or deleting a UMA policy associated with multiple resources, the authorization check only verifies the caller's ownership against the first resource in the policy's list. This allows a user (Owner A) who owns one resource (RA) to update a shared policy and modify authorization rules for other resources (e.g., RB) in that same policy, even if those other resources are owned by a different user (Owner B). This constitutes a horizontal privilege escalation.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.keycloak:keycloak-services | all versions | 26.2.13org.keycloak:keycloak-services:26.2.13 |
| ☕Maven | org.keycloak:keycloak-services | ≥ 26.5.0&&< 26.5.3 | 26.5.3org.keycloak:keycloak-services:26.5.3 |
| ☕Maven | org.keycloak:keycloak-services | ≥ 26.3.0&&< 26.4.9 | 26.4.9org.keycloak:keycloak-services:26.4.9 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-services, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.keycloak:keycloak-services to 26.2.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-14778 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2025-14778 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Keycloak 26.2 | rhbk/keycloak-operator-bundle:26.2.13-1 | RHSA-2026:2364 |
| Red Hat build of Keycloak 26.2.13 | rhbk/keycloak-rhel9-operator | RHSA-2026:2363 |
| Red Hat build of Keycloak 26.4 | rhbk/keycloak-operator-bundle:26.4.9-1 | RHSA-2026:2366 |
| Red Hat build of Keycloak 26.4.9 | rhbk/keycloak-rhel9-operator | RHSA-2026:2365 |
Frequently Asked Questions
Is CVE-2025-14778 in your dependencies?
Find it across Maven, including transitive dependencies.