dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2025-7784

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a privilege escalation vulnerability in Keycloak where Fine-Grained Admin Permissions (FGAPv2) improperly allow users with only the manage-users role to escalate to realm-admin level access. The flaw compromises the intended role-based access control separation in Keycloak's administrative model.

MitigationApply the vendor-supplied patch or upgrade Keycloak to the version that fixes this FGAPv2 privilege enforcement issue, and audit existing admin role assignments after patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of KeycloakApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Keycloak is running
    Access the Keycloak admin console or check the service status via system commands (systemctl status keycloak or equivalent)
    Affected if Keycloak instance is active and accessible
  2. Identify if FGAPv2 is enabled
    Check the Keycloak realm settings for Fine-Grained Admin Permissions v2 configuration. This is typically found in Realm Settings > Admin Permissions or via the admin API endpoint for realm roles. Inspect whether FGAPv2 permission model is active for the realm.
    Affected if FGAPv2 permission model is enabled for the realm being assessed
  3. List users with manage-users role
    In Keycloak admin console, navigate to Users > Role Mappings or use the admin API to query users assigned the 'manage-users' realm role. Run: keycloak-admin users list with realm-admin credentials and filter for manage-users role assignment.
    Affected if Any service accounts or users are assigned the manage-users role under FGAPv2
  4. Check for improper privilege escalation
    Review the effective permissions for users holding only the manage-users role. Verify if these users have realm-admin or elevated admin permissions they should not possess. In the admin console, select each manage-users account and inspect their Role Mappings to confirm whether realm-admin is erroneously assigned.
    Affected if Users with only manage-users role have realm-admin or equivalent elevated privileges assigned

A user is affected if Keycloak with FGAPv2 enabled has users assigned the manage-users role who have improperly obtained realm-admin level access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch or upgrade Keycloak to the version that fixes this FGAPv2 privilege enforcement issue, and audit existing admin role assignments after patching.

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7784 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7784 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data