NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Keycloak: Unauthorized access via improper validation of encrypted SAML assertionsGHSA-794g-x443-36f7

HIGHFix: keycloak/keycloak#46929

GHSA-794g-x443-36f7 is a high-severity (CVSS 7.7) CWE-1287 vulnerability in org.keycloak:keycloak-services. A fix is available for org.keycloak:keycloak-services — see the affected versions and patch details below.

Also known asBIT-keycloak-2026-2092CVE-2026-2092
Published
Updated
Affected
3 pkgs
Patched
1 / 3
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 GHSA-794g-x443-36f7.

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
0.00%0.29%0.58%0.88%0.1%0.4%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
☕org.keycloak:keycloak-services☕org.keycloak:keycloak-services☕org.keycloak:keycloak-services

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven 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

3 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.keycloak:keycloak-servicesall versionsNo fix
☕Mavenorg.keycloak:keycloak-services≥ 26.3.0No fix
☕Mavenorg.keycloak:keycloak-services≥ 26.5.0&&< 26.5.526.5.5org.keycloak:keycloak-services:26.5.5

Affected Products

1 product · 2 configurations
Application
build of keycloakredhat
≥ 26.4 && < 26.4.10
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    A fix is available for GHSA-794g-x443-36f7; check the affected-versions list above or the advisory for the patched release of org.keycloak:keycloak-services, then make sure no transitive dependency still pins the vulnerable range.

  3. 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 GHSA-794g-x443-36f7 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat build of Keycloak 26.2rhbk/keycloak-operator-bundle:26.2.14-1RHSA-2026:3925
Red Hat build of Keycloak 26.2.14rhbk/keycloak-rhel9RHSA-2026:3926
Red Hat build of Keycloak 26.4rhbk/keycloak-operator-bundle:26.4.10-1RHSA-2026:3948
Red Hat build of Keycloak 26.4.10rhbk/keycloak-rhel9RHSA-2026:3947
Red Hat Single Sign-On 7.6.13keycloak-servicesRHSA-2026:76132
Red Hat Single Sign-On 7.6 for RHEL 7rh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el7ssoRHSA-2026:76128
Red Hat Single Sign-On 7.6 for RHEL 8rh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el8ssoRHSA-2026:76129
Red Hat Single Sign-On 7.6 for RHEL 9rh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el9ssoRHSA-2026:76130

Frequently Asked Questions

Keycloak's 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, injecting an encrypted assertion for an arbitrary principal, leading to unauthorized access and potential information disclosure.
O3 Security · Impact-Aware SCA

Is GHSA-794g-x443-36f7 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Keycloak: Unauthorized access via improper validation of…