Incorrect Privilege Assignment Affecting keycloak-doc package, versions <26.5.3-r0


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.01% (1st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Incorrect Privilege Assignment vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-KEYCLOAKDOC-15267010
  • published12 Feb 2026
  • disclosed9 Feb 2026

Introduced: 9 Feb 2026

NewCVE-2025-14778  (opens in a new tab)
CWE-266  (opens in a new tab)

How to fix?

Upgrade Minimos:latest keycloak-doc to version 26.5.3-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream keycloak-doc package and not the keycloak-doc package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

A flaw was found in Keycloak. A significant Broken Access Control vulnerability exists in the UserManagedPermissionService (UMA Protection API). When updating or deleting a UMA policy associated with multiple resources, the authorization check only verifies the caller's ownership against the first resource in the policy's list. This allows a user (Owner A) who owns one resource (RA) to update a shared policy and modify authorization rules for other resources (e.g., RB) in that same policy, even if those other resources are owned by a different user (Owner B). This constitutes a horizontal privilege escalation.

CVSS Base Scores

version 3.1