dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2026-14614

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-03
Fix available
A fix is available. Upgrade to 26.4.14 / 26.6.5 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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 ClientResource component of Keycloak's admin services when Fine-Grained Admin Permissions (FGAP) v2 is enabled. This issue allows a delegated administrator, who should only have limited control over specific clients, to attach or remove hidden client scopes that they are not authorized to see or manage. As a result, an attacker could inject unauthorized data or permissions into the security tokens issued to end-users, potentially tricking other applications into granting higher levels of access than intended.

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 · moderate confidence

In Keycloak with Fine-Grained Admin Permissions v2 (FGAPv2) enabled, the ClientResource component fails to properly restrict delegated administrators from attaching or removing hidden client scopes they are not authorized to manage. This permission bypass allows limited admins to modify security token generation by adding unauthorized client scopes, potentially escalating privileges in downstream applications that trust Keycloak-issued tokens.

MitigationEnsure FGAPv2 configurations strictly enforce scope-level permissions for delegated administrators, preventing access to hidden client scopes. Consider reviewing and restricting admin role assignments until an official patch is applied.

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:>= 26.4, < 26.4.14>= 26.6, < 26.6.5

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Verify FGAP v2 is enabled
    In Keycloak admin console, go to Realm Settings > General tab and check if 'Fine-Grained Admin Permissions' is enabled, or query the realm representation via API: GET /admin/realms/{realm} and look for 'fineGrainedPermissionEnabled' set to true
    Affected if FGAP v2 is enabled (fineGrainedPermissionEnabled = true)
  2. Identify delegated admins with client permissions
    In Keycloak admin console, go to Users or Roles section and look for users/role composites that have client-level admin permissions (admin-permissions on specific clients), or query: GET /admin/realms/{realm}/clients/{client-uuid}/roles and review role assignments
    Affected if Delegated administrators exist with client-scoped admin roles that can manage client scopes
  3. Review client scope assignments for unauthorized scopes
    Query client scopes for each client: GET /admin/realms/{realm}/clients/{client-uuid}/client-scopes and compare against what the delegated admin should have access to. Check both 'default' and 'optional' client scope mappings
    Affected if Hidden or sensitive client scopes (e.g., groups, roles, audience) are attached to clients that the delegated admin should not be able to modify
  4. Audit client scope permission grants
    Check the permission representation for client scopes: GET /admin/realms/{realm}/clients/{client-uuid}/evaluate-scopes and review which scopes the current user is authorized to manage. Also check Realm Authorization settings for scope-based permissions
    Affected if The delegated admin can attach scopes they are not explicitly authorized to manage per FGAP permissions

User is affected if FGAP v2 is enabled AND they have delegated administrators with client-level permissions that can modify client scopes beyond their intended authorization.

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
Upgrade available Upgrade to 26.4.14 / 26.6.5 or later
Fixed in 26.4.1426.6.5
Interim mitigation

Ensure FGAPv2 configurations strictly enforce scope-level permissions for delegated administrators, preventing access to hidden client scopes. Consider reviewing and restricting admin role assignments until an official patch is applied.

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14614 — 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-2026-14614 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