dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2026-2092

HIGH · 7.7 CVSS v3.1 Published 2026-03-18
Fix available
A fix is available. Upgrade to 26.2.14 / 26.4.10 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Keycloak's SAML broker endpoint fails to validate encrypted assertions when the SAML response itself is not signed. An attacker possessing a valid signed SAML assertion can inject a crafted malicious response containing an encrypted assertion for an arbitrary principal, bypassing authentication and gaining unauthorized access.

MitigationEnsure SAML responses are signed and configure Keycloak to require signature validation on both the response and assertions. Apply available Keycloak security patches for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of KeycloakApplication
Affected:>= 26.2, < 26.2.14>= 26.4, < 26.4.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Keycloak version
    Check the Keycloak version by inspecting the startup logs, the keycloak-server.json configuration file, or the /health/ready endpoint. Compare the installed version against the Keycloak release versions that include the fix for CVE-2026-2092.
    Affected if The installed Keycloak version is older than the version containing the security fix for this vulnerability.
  2. Determine if SAML broker is configured
    Review the Keycloak realm configuration or the broker settings for the realm. Look for SAML identity provider configurations under the Identity Providers section in the admin console or the realm JSON configuration.
    Affected if A SAML identity provider (broker) is configured and accepting SAML responses.
  3. Verify SAML response signature requirement
    Inspect the SAML broker settings for the 'Sign SAML Response' or 'Sign Assertions' option. Check the identity provider configuration in the realm settings or the SAML endpoint configuration to see whether the 'Want AuthnRequest Signed' or 'Validate Signature' settings are enforced.
    Affected if The SAML response signature is not required (set to optional or disabled), allowing unsigned responses to be accepted.
  4. Check encrypted assertion validation
    Examine the SAML identity provider configuration for settings related to 'Encrypt Assertions' or 'Validate Encrypted Assertions'. Review the Keycloak SAML broker logs or enable debug logging to observe how encrypted assertions are processed when the response is unsigned.
    Affected if Encrypted assertions are not validated independently of the overall response signature, or there is no explicit validation step for encrypted assertions when the response is unsigned.

A Keycloak instance is affected if it runs an unpatched version with a SAML broker configured that does not enforce signed SAML responses and fails to validate encrypted assertions independently.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 26.2.14 / 26.4.10 or later
Fixed in 26.2.1426.4.10
Interim mitigation

Ensure SAML responses are signed and configure Keycloak to require signature validation on both the response and assertions. Apply available Keycloak security patches for this vulnerability.

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2092 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2092 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data