GHSA-27gp-8389-hm4w CVE-2025-7784

Keycloak Privilege Escalation Vulnerability in Admin Console (FGAPv2 Enabled)

Medium Maven

Severity: 6.5 / 10; Medium · CVSS 3.1
Exploit chance (EPSS): 0.45%; Chance of exploitation in the next 30 days. Higher than 39.27% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-269 Improper Privilege Management
Fix: 26.2.6; Upgrade org.keycloak:keycloak-services to this version or later

Description

A Privilege Escalation vulnerability was identified in the Keycloak identity and access management solution, specifically when FGAPv2 is enabled in version 26.2.x. The flaw lies in the admin permission enforcement logic, where a user with manage-users privileges can self-assign realm-admin rights. The escalation occurs due to missing privilege boundary checks in role mapping operations via the admin REST interface. A malicious administrator with limited permissions can exploit this by editing their own user roles, gaining unauthorized full access to realm configuration and user data.

This issue has been fixed in versions 26.2.6, and 26.3.0.

Affected versions

Maven

Package	Vulnerable	Fixed in
org.keycloak:keycloak-services	`>= 26.2.0, < 26.2.6`	`26.2.6`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.keycloak:keycloak-services Maven → `26.2.6`

maven

<dependency><groupId>org.keycloak</groupId><artifactId>keycloak-services</artifactId><version>26.2.6</version></dependency>

gradle

implementation("org.keycloak:keycloak-services:26.2.6")

Severity breakdown

CVSS 3.1 6.5

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Attack vector: Network
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Weakness

CWE-269: Improper Privilege Management

The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.

How to prevent it

Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design: Follow the principle of least privilege when assigning access rights to entities in a software system.
Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2025-7784

Packages

github.com/keycloak/keycloak

Timeline

Jul 18, 2025 Published
Jun 17, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-v3f7-2p4r-mwfw Keycloak vulnerable to cross-site scripting (xss) via case-insensitive uri validation bypass	High	Also affects org.keycloak:keycloak-services
GHSA-9jrw-8xf7-xqhq Keycloak vulnerable to information disclosure through arbitrary filesystem path probing	Medium	Also affects org.keycloak:keycloak-services
GHSA-w3p3-7cjg-vgfw Keycloak allows unauthorized access to resources via uma permission ticket bypass	Medium	Also affects org.keycloak:keycloak-services
GHSA-f5p5-6xmx-p252 Keycloak vulnerable to authorization bypass via incorrect uri comparison	High	Also affects org.keycloak:keycloak-services
GHSA-r7rc-c989-86g6 Keycloak: Attacker can re-enable and take over disabled clients via registration access token	Medium	Also affects org.keycloak:keycloak-services
GHSA-4gv3-mc9p-5wqc Keycloak: Unauthenticated account takeover via reset-credentials flow bypass	Critical	Also affects org.keycloak:keycloak-services
GHSA-6g26-7cx5-mrrg Keycloak: Information disclosure due to user profile permission bypass	Low	Also affects org.keycloak:keycloak-services
GHSA-cpf7-j4cf-vqx4 Keycloak has an Out-of-bounds Read	Medium	Also affects org.keycloak:keycloak-services

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor