# Keycloak Affected by Broken Access Control Vulnerability in the UserManagedPermissionService

Advisory record · `GHSA-fm6w-rrp3-2x4w`

- **Identifiers:** `GHSA-fm6w-rrp3-2x4w` · `CVE-2025-14778`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-266](https://cwe.mitre.org/data/definitions/266.html)
- **Tags:** [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.md)
- **Published:** 9 Feb 2026
- **Updated:** 13 Feb 2026
- **Reviewed by a person:** No

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

## Affected packages

- `org.keycloak:keycloak-services` (Maven): affected `<26.2.13 || >=26.5.0, <26.5.3 || >=26.3.0, <26.4.9`; fixed in `26.2.13`, `26.5.3`, `26.4.9`

## Machine-written summary

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

> Keycloak (org.keycloak:keycloak-services, which is the Maven artifact) is affected in versions before 26.2.13, from 26.3.0 before 26.4.9, and from 26.5.0 before 26.5.3. When a UMA policy covers multiple resources, updating or deleting it checks ownership only against the first resource, so a user who owns one resource can change the policy's rules on resources owned by someone else. Upgrade to 26.2.13, 26.4.9, 26.5.3, or a later fixed release.

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

- 5.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`, from CNA (redhat)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0032, the 25th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:21 UTC: First seen by agentprime
- 31 Oct 2026, 14:21 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-fm6w-rrp3-2x4w)

## Sources

- [GitHub Advisory Database: GHSA-fm6w-rrp3-2x4w](https://github.com/advisories/GHSA-fm6w-rrp3-2x4w)
- [OSV: GHSA-fm6w-rrp3-2x4w](https://osv.dev/vulnerability/GHSA-fm6w-rrp3-2x4w)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-14778>
- <https://github.com/keycloak/keycloak/issues/46147>
- <https://github.com/keycloak/keycloak/pull/46154>
- <https://access.redhat.com/errata/RHSA-2026:2363>
- <https://access.redhat.com/errata/RHSA-2026:2364>
- <https://access.redhat.com/errata/RHSA-2026:2365>
- <https://access.redhat.com/errata/RHSA-2026:2366>
- <https://access.redhat.com/security/cve/CVE-2025-14778>
- <https://bugzilla.redhat.com/show_bug.cgi?id=2422600>
- <https://github.com/keycloak/keycloak>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-fm6w-rrp3-2x4w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-fm6w-rrp3-2x4w/>. Everything for agents: <https://agentprime.io/llms.txt>.