How severe is CVE-2026-2092?

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

Which packages are affected by CVE-2026-2092?

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

How do I fix CVE-2026-2092?

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

How do I detect CVE-2026-2092 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-2092 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

No public exploit code has been indexed for CVE-2026-2092 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-2092?

CVE-2026-2092 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th 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-2092?

CVE-2026-2092 is classified as CWE-1287 (CWE-1287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2026-2092?

14 Metasploit modules reference CVE-2026-2092, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

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

CVE-2026-2092 was published on August 25, 2026 and was last updated on October 7, 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-2092 — keycloak

CVE-2026-2092 is a CWE-1287 vulnerability in keycloak. A fix is available for keycloak — see the affected versions and patch details below.

Keycloak-services: keycloak: unauthorized access via improper validation of encrypted saml assertions

Also known asGHSA-794g-x443-36f7

Published

Aug 25, 2026

Updated

Oct 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 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-2092.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs31th percentile — riskier than 31% 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. Keycloak's Security Assertion Markup Language (SAML) broker endpoint does not properly validate encrypted assertions when the overall SAML response is not signed. An attacker with a valid signed SAML assertion can exploit this by crafting a malicious SAML response. This allows the attacker to inject an encrypted assertion for an arbitrary principal, leading to unauthorized access and potential information disclosure.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`keycloak`	≥ 26.2.0&&< 26.2.14	26.2.14

Affected Products

1 product · 2 configurations

Application

build of keycloakredhat

≥ 26.4 && < 26.4.10

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.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-2092 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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 HatImportant

The issue is rated as important severity. A flaw in Red Hat Build of Keycloak's SAML broker endpoint allows unauthorized access. When the overall SAML response is not signed, an attacker with a valid signed SAML assertion can craft a malicious response to inject an encrypted assertion for an arbitrary principal. This…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

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

Product	Fixed in	Advisory
Red Hat build of Keycloak 26.2	`rhbk/keycloak-operator-bundle:26.2.14-1`	RHSA-2026:3925
Red Hat build of Keycloak 26.2.14	`rhbk/keycloak-rhel9`	RHSA-2026:3926
Red Hat build of Keycloak 26.4	`rhbk/keycloak-operator-bundle:26.4.10-1`	RHSA-2026:3948
Red Hat build of Keycloak 26.4.10	`rhbk/keycloak-rhel9`	RHSA-2026:3947
Red Hat Single Sign-On 7.6.13	`keycloak-services`	RHSA-2026:76132
Red Hat Single Sign-On 7.6 for RHEL 7	`rh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el7sso`	RHSA-2026:76128
Red Hat Single Sign-On 7.6 for RHEL 8	`rh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el8sso`	RHSA-2026:76129
Red Hat Single Sign-On 7.6 for RHEL 9	`rh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el9sso`	RHSA-2026:76130

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-2092 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works