REDHAT-BUG-2503139: High severity Keycloak Keycloak vulnerability

Published Jul 21, 2026
·
Updated

A vulnerability was identified in Keycloak where the SAML Identity Provider IdP metadata parser incorrectly configures signature validation. When a metadata document is imported that sets WantAuthnRequestsSigned to false and includes a KeyDescriptor without an explicit use attribute, the parser stores the certificate but fails to enable the validateSignature setting. As a result, the broker endpoint /realms/realm/broker/alias/endpoint does not verify the cryptographic signature of incoming SAML responses. An unauthenticated remote attacker can exploit this by capturing a valid RelayState and SAML request ID through a standard login flow and then submitting a forged, unsigned SAML response. By providing the external SAML NameID of a target user, the attacker can successfully authenticate as that user. Successful exploitation allows an attacker to: Bypass authentication mechanisms.

Impersonate any user who has a federated identity link.

Access and modify data belonging to the compromised user account.

Affected Software

1 affected component
Keycloak Keycloak

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Ensure Keycloak enables cryptographic signature validation for incoming SAML responses at /realms/realm/broker/alias/endpoint (i.e., the metadata import must result in validateSignature being enabled, not silently left disabled when a metadata document sets WantAuthnRequestsSigned to false).

    Keycloak SAML IdP metadata parser / broker endpoint (/realms/realm/broker/alias/endpoint) validateSignature = true

Event History

Jul 21, 2026
Data Sourced
via Red Hat·07:41 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-2503139?

The severity of REDHAT-BUG-2503139 is classified as high with a score of 7.

2

How do I fix REDHAT-BUG-2503139?

To fix REDHAT-BUG-2503139, update to the latest patched version of Keycloak that addresses this vulnerability.

3

What are the potential impacts of REDHAT-BUG-2503139?

The potential impacts of REDHAT-BUG-2503139 include unauthorized access due to improper signature validation in the SAML IdP metadata parser.

4

When was REDHAT-BUG-2503139 published?

REDHAT-BUG-2503139 was published on July 21, 2026.

5

What software is affected by REDHAT-BUG-2503139?

The affected software by REDHAT-BUG-2503139 is Keycloak.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203