# CVE-2025-14083: Keycloak-server: keycloak: improper access control in admin rest api leads to information disclosure

> Improper access control in Keycloak Admin REST API exposes backend schema and rules, enabling information disclosure and potential privilege escalation.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jan 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-594w-2fwp-jwrc, MINI-h2xr-jpqj-f92c

## What is CVE-2025-14083?

CVE-2025-14083 is a low-severity vulnerability in Red Hat build of Keycloak 26.4, published on 21 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in the Keycloak Admin REST API. This vulnerability allows the exposure of backend schema and rules, potentially leading to targeted attacks or privilege escalation via improper access control.

Weakness: CWE-284 (Improper Access Control)

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

2 open source packages ship an affected version, including org.keycloak:keycloak-services.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | All versions to 26.2.5 | None |
| `org.keycloak:keycloak-services` | Maven | All versions to 26.2.5 | None |

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

Upgrade to a fixed version.

## Is CVE-2025-14083 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14083 is a low-severity vulnerability in Red Hat build of Keycloak 26.4, published on 21 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14083 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions up to 26.2.5; no fix listed
- org.keycloak:keycloak-services (Maven): affected all versions up to 26.2.5; no fix listed

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

## Sources

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

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