Skip to content
Fencer Vulns
low 2.7

CVE-2025-14083 json

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

published 2026-01-21 9 mo ago modified 2026-06-17 4 mo ago also GHSA-594w-2fwp-jwrc , EUVD-2026-3683

cvss
2.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

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.

Patch / fix

  • Red Hat Red Hat build of Keycloak 26.4 26.4-14, 26.4.11-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-14083 updated cvss 2.7

keycloak-server: Keycloak: Improper Access Control in Admin REST API leads to information disclosure

  • Red Hat build of Keycloak 26.4 rhbk/keycloak-rhel9 26.4-14, rhbk/keycloak-rhel9-operator 26.4-14, rhbk/keycloak-operator-bundle 26.4.11-1
    fixed: vendor fix RHSA-2026:6478
  • Red Hat build of Keycloak 26.4.11
    fixed: vendor fix RHSA-2026:6477

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9 mo ago

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-services
<=26.2.5
no fix listed

Affected products

  • Red Hat Red Hat build of Keycloak 26.4
  • Red Hat Red Hat build of Keycloak 26.4.11

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.