# CVE-2025-14777: Keycloak: keycloak idor in realm client creating/deleting

> Authenticated attackers with limited admin rights can delete or modify resources of other clients in the same realm due to improper access control checks.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2025
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-4cj5-g32w-86fv

## What is CVE-2025-14777?

CVE-2025-14777 is a medium-severity missing authorization vulnerability in Red Hat build of Keycloak 26.4, published on 16 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in Keycloak. An IDOR (Broken Access Control) vulnerability exists in the admin API endpoints for authorization resource management, specifically in ResourceSetService and PermissionTicketService. The system checks authorization against the resourceServer (client) ID provided in the API request, but the backend database lookup and modification operations (findById, delete) only use the resourceId. This mismatch allows an authenticated attacker with fine-grained admin permissions for one client (e.g., Client A) to delete or update resources belonging to another client (Client B) within the same realm by supplying a valid resource ID.

Weakness: CWE-289 (Authentication Bypass by Alternate Name)

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


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

No fix has been published for CVE-2025-14777 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14777 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14777 is a medium-severity missing authorization vulnerability in Red Hat build of Keycloak 26.4, published on 16 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14777 in the wild and no public exploit code.

Affected product: Red Hat build of Keycloak 26.4. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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