# CVE-2025-14778: Keycloak: incorrect ownership checks in /uma-policy/

> Attackers can modify authorization rules for resources they do not own by exploiting incorrect ownership checks in the UMA Protection API.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Feb 2026
- **Updated:** 10 Feb 2026
- **Also known as:** ECHO-a380-e585-5861, GHSA-fm6w-rrp3-2x4w, MINI-29v2-j8ww-hp96, MINI-2g82-mfv8-7jcc

## What is CVE-2025-14778?

CVE-2025-14778 is a medium-severity missing authorization vulnerability in Red Hat build of Keycloak 26.2, published on 9 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-14778?

6 open source packages ship an affected version, including org.keycloak:keycloak-services.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | All versions | 26.2.13 |
| `org.keycloak:keycloak-services` | Maven | All versions | 26.2.13 |
| `org.keycloak:keycloak-services` | Maven | From 26.3.0 | 26.4.9 |
| `org.keycloak:keycloak-services` | Maven | From 26.3.0 | 26.4.9 |
| `org.keycloak:keycloak-services` | Maven | From 26.5.0 | 26.5.3 |
| `org.keycloak:keycloak-services` | Maven | From 26.5.0 | 26.5.3 |

## How do I fix CVE-2025-14778?

Upgrade org.keycloak:keycloak-services to a fixed version for your release line: 26.2.13, 26.4.9 or 26.5.3.

## Is CVE-2025-14778 being exploited?

There is no known exploitation of CVE-2025-14778 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14778 and fix it if it is affected.

What it is: CVE-2025-14778 is a medium-severity missing authorization vulnerability in Red Hat build of Keycloak 26.2, published on 9 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14778 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.2.13
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.2.13
- org.keycloak:keycloak-services (Maven): affected from 26.3.0; fixed in 26.4.9
- org.keycloak:keycloak-services (Maven): affected from 26.3.0; fixed in 26.4.9
- org.keycloak:keycloak-services (Maven): affected from 26.5.0; fixed in 26.5.3
- org.keycloak:keycloak-services (Maven): affected from 26.5.0; fixed in 26.5.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14778/ (Markdown: https://insights.sbomify.com/CVE-2025-14778/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14778
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14778
- OSV: https://osv.dev/vulnerability/CVE-2025-14778

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14778/
Summaries are generated and may contain mistakes; the official description above is the record.