Answer in brief
CVE-2026-2092 records a High severity (CVSS 7.7) vulnerability in Keycloak: Unauthorized access via improper validation of encrypted SAML assertions. The current sources do not mark it as known exploited. The current feed maps org.keycloak:keycloak-services (maven), org.keycloak:keycloak-services (maven), org.keycloak:keycloak-services (maven), org.keycloak:keycloak-services (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps org.keycloak:keycloak-services (maven), org.keycloak:keycloak-services (maven), org.keycloak:keycloak-services (maven), org.keycloak:keycloak-services (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:redhat:build_of_keycloak:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| org.keycloak:keycloak-servicesmaven | <=26.2.5 | Not reported |
| org.keycloak:keycloak-servicesmaven | >=26.3.0,<=26.4.7 | Not reported |
| org.keycloak:keycloak-servicesmaven | >=26.5.0,<26.5.5 | Not reported |
| org.keycloak:keycloak-servicesmaven | >=0 | Not reported |
| org.keycloak:keycloak-servicesmaven | >=26.3.0 | Not reported |
| org.keycloak:keycloak-servicesmaven | >=26.5.0 | Not reported |
Published upstream
Mar 18, 2026
Evidence: source:nvd:source_dates:source-dates:recordSource modified
Aug 26, 2026
Evidence: source:nvd:source_dates:source-dates:recordFirst seen by HOL
Jul 2, 2026
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.
Quoted source text, attributed separately from HOL analysis.