# CVE-2025-7784: Org.keycloak/keycloak-services: privilege escalation in keycloak admin console (fgapv2 enabled)

> Administrative users with manage-users role can escalate to realm-admin in Keycloak when Fine-Grained Admin Permissions are enabled.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jul 2025
- **Updated:** 6 May 2026
- **Also known as:** GHSA-27gp-8389-hm4w, MINI-7rq9-2q68-x4j8

## What is CVE-2025-7784?

CVE-2025-7784 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 18 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in the Keycloak identity and access management system when Fine-Grained Admin Permissions(FGAPv2) are enabled. An administrative user with the manage-users role can escalate their privileges to realm-admin due to improper privilege enforcement. This vulnerability allows unauthorized elevation of access rights, compromising the intended separation of administrative duties and posing a security risk to the realm.

Weakness: CWE-269 (Improper Privilege Management)

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

2 open source packages ship an affected version, including org.keycloak:keycloak-services. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | From 26.2.0 | 26.2.6 |
| `org.keycloak:keycloak-services` | Maven | From 26.2.0 | 26.2.6 |

Products: Redhat Build of Keycloak.

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

Upgrade org.keycloak:keycloak-services to 26.2.6 or later.

## Is CVE-2025-7784 being exploited?

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

## Other vulnerabilities in Redhat Build of Keycloak

- [CVE-2026-15572](https://insights.sbomify.com/CVE-2026-15572/): Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation (high 8.8)
- [CVE-2026-3047](https://insights.sbomify.com/CVE-2026-3047/): Keycloak SAML Broken has Authentication Bypass by Primary Weakness (high 8.8)
- [CVE-2026-15573](https://insights.sbomify.com/CVE-2026-15573/): Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher (high 8.1)
- [CVE-2026-16102](https://insights.sbomify.com/CVE-2026-16102/): Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers (high 8.1)
- [CVE-2026-1609](https://insights.sbomify.com/CVE-2026-1609/): Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7784 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 18 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7784 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected from 26.2.0; fixed in 26.2.6
- org.keycloak:keycloak-services (Maven): affected from 26.2.0; fixed in 26.2.6

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-7784/ (Markdown: https://insights.sbomify.com/CVE-2025-7784/index.md)
```

## Sources

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

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