How severe is CVE-2026-9083?

No CVSS score has been assigned to CVE-2026-9083 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-9083?

CVE-2026-9083 affects the following packages: keycloak (Bitnami). Ecosystems affected: Bitnami.

How do I fix CVE-2026-9083?

Update keycloak to 26.4.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-9083 is resolved across your whole dependency graph.

How do I detect CVE-2026-9083 in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keycloak, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-9083 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-9083 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-9083 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-9083?

CVE-2026-9083 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-9083?

CVE-2026-9083 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-9083 published, and has it been updated?

CVE-2026-9083 was published on August 25, 2026 and was last updated on October 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

Not in CISA KEV

CVE-2026-9083 — keycloak

CVE-2026-9083 is a Path Traversal vulnerability in keycloak. A fix is available for keycloak — see the affected versions and patch details below.

Keycloak: keycloak: information disclosure through arbitrary filesystem path probing

Also known asGHSA-9jrw-8xf7-xqhq

Published

Aug 25, 2026

Updated

Oct 29, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-9083.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦keycloak

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`keycloak`	≥ 26.4.0&&< 26.4.13	26.4.13

Affected Products

1 product · 2 configurations

Application

build of keycloakredhat

≥ 26.6 && < 26.6.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keycloak, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update keycloak to 26.4.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-9083 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Medium: This flaw in Keycloak allows a highly privileged realm administrator with the "manage-realm" role to perform arbitrary filesystem path probing. By submitting a crafted keystore path, an authenticated attacker can determine the existence and readability of files on the Keycloak server, potentially identifying…

Workaround published by Red Hat

Ensure that only highly trusted administrators are granted the "manage-realm" role within Keycloak. This role provides extensive administrative privileges, including the ability to exploit this vulnerability for filesystem probing. Regularly review and audit users assigned to this role to minimize the attack surface.

Source: Red Hat security advisory for CVE-2026-9083 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat build of Keycloak 26.4	`rhbk/keycloak-operator-bundle:26.4.13-1`	RHSA-2026:30050
Red Hat build of Keycloak 26.4.13	`rhbk/keycloak-rhel9`	RHSA-2026:30049
Red Hat build of Keycloak 26.6	`rhbk/keycloak-operator-bundle:26.6.4-2`	RHSA-2026:30084
Red Hat build of Keycloak 26.6.4	`rhbk/keycloak-rhel9`	RHSA-2026:30083

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-9083 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works