Keycloak: Unauthorized access via improper validation of encrypted SAML assertions
CVE-2026-2092 · GHSA-794g-x443-36f7 · BIT-keycloak-2026-2092 · published 2 Jul 2026
How serious is it
- Severity: high, CVSS score 7.7 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-2092?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
org.keycloak:keycloak-services(Maven) <= 26.2.5org.keycloak:keycloak-services(Maven) >= 26.3.0, <= 26.4.7org.keycloak:keycloak-services(Maven) >= 26.5.0, < 26.5.5
How to check
- Look for
org.keycloak:keycloak-servicesin your lockfile and compare its version with the range above. - Or paste your lockfile into the checker: it lists every package with a known vulnerability, this one included.
How to fix
Copies a prompt for Claude Code, Cursor or Codex: it checks your lockfiles for this and upgrades it.
- No fixed version of
org.keycloak:keycloak-servicesyet. Replace or remove it, or apply the workaround in the advisory below. - No fixed version of
org.keycloak:keycloak-servicesyet. Replace or remove it, or apply the workaround in the advisory below. - On >= 26.5.0, < 26.5.5: Upgrade
org.keycloak:keycloak-servicesto 26.5.5 or later, commit the lockfile and redeploy. - If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- github.com/keycloak/keycloak/security/advisories/GHSA-794g-x443-36f7
- nvd.nist.gov/vuln/detail/CVE-2026-2092
- github.com/keycloak/keycloak/pull/46929
- github.com/keycloak/keycloak/commit/b40a25908d937bb0563ea516487bc2c7c1d92508
- access.redhat.com/errata/RHSA-2026:3925
- access.redhat.com/errata/RHSA-2026:3926
- access.redhat.com/errata/RHSA-2026:3947
- access.redhat.com/errata/RHSA-2026:3948
- access.redhat.com/security/cve/CVE-2026-2092
- bugzilla.redhat.com/show_bug.cgi?id=2437296
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-2092.json
- github.com/advisories/GHSA-794g-x443-36f7
- github.com/keycloak/keycloak
Merged from GitHub Advisory Database, OSV. Last updated 27 Oct 2026. All vulnerabilities · RSS · JSON