Skip to content
Fencer Intel
medium 4.9

CVE-2026-9083 json

Keycloak: keycloak: information disclosure through arbitrary filesystem path probing

published 4mo ago modified 13d ago also BIT-keycloak-2026-9083 , EUVD-2026-39476 , GHSA-9jrw-8xf7-xqhq

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

Summary

A flaw was found in Keycloak. A realm administrator with the "manage-realm" role can exploit this vulnerability by submitting an arbitrary filesystem path as a keystore parameter when creating a key provider component. This allows the administrator to probe arbitrary filesystem paths, determining which files exist and are readable by the Keycloak process. This information disclosure could be used to identify high-value targets for follow-on attacks.

Patch / fix

  • maven org.keycloak:keycloak-services 26.6.4
  • bitnami keycloak 26.4.13, 26.6.4
  • Red Hat Red Hat build of Keycloak 26.4 26.4-19, 26.4.13-1
  • Red Hat Red Hat build of Keycloak 26.6 26.6-8, 26.6.4-2

Is CVE-2026-9083 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2026-9083 updated cvss 4.9

keycloak: Keycloak: Information disclosure through arbitrary filesystem path probing

  • Red Hat build of Keycloak 26.4 rhbk/keycloak-rhel9 26.4-19, rhbk/keycloak-rhel9-operator 26.4-19, rhbk/keycloak-operator-bundle 26.4.13-1
    fixed: vendor fix RHSA-2026:30050
  • Red Hat build of Keycloak 26.4.13
    fixed: vendor fix RHSA-2026:30049
  • Red Hat build of Keycloak 26.6 rhbk/keycloak-rhel9 26.6-8, rhbk/keycloak-rhel9-operator 26.6-8, rhbk/keycloak-operator-bundle 26.6.4-2
    fixed: vendor fix RHSA-2026:30084
  • Red Hat build of Keycloak 26.6.4
    fixed: vendor fix RHSA-2026:30083

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
4mo ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-services
<26.6.4
26.6.4
bitnami keycloak
>=26.4.0, <26.4.13
>=26.6.0, <26.6.4
26.4.13
26.6.4

Affected products

  • Red Hat Red Hat build of Keycloak 26.4
  • Red Hat Red Hat build of Keycloak 26.4.13
  • Red Hat Red Hat build of Keycloak 26.6
  • Red Hat Red Hat build of Keycloak 26.6.4

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel 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.