CVE-2026-16443
Received Received - Intake

SAML Signature Bypass in Red Hat Keycloak

Vulnerability report for CVE-2026-16443, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-05

Last updated on: 2026-08-05

Assigner: Red Hat, Inc.

Description

A flaw was found in the SAML metadata import functionality of the keycloak-services component, which is the core engine for identity brokering in Red Hat Build of Keycloak. When importing identity provider metadata that lacks specific usage attributes for keys, the system incorrectly disables signature validation for SAML responses even if a signing certificate is provided. This issue allows an unauthenticated attacker to forge a SAML response and gain unauthorized access to a user account by knowing their external identifier.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-05
Last Modified
2026-08-05
Generated
2026-08-05
AI Q&A
2026-08-05
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
red_hat keycloak *
red_hat keycloak From 0.0.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-347 The product does not verify, or incorrectly verifies, the cryptographic signature for data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-16443 is a flaw in Keycloak's SAML Identity Provider metadata parser. When importing SAML metadata that sets 'WantAuthnRequestsSigned' to false and includes a KeyDescriptor without an explicit use attribute, the parser fails to enable signature validation for SAML responses. This allows an unauthenticated attacker to forge unsigned SAML responses and impersonate users by providing their external identifier.

Detection Guidance

To detect this vulnerability, check Keycloak logs for SAML metadata import events where the 'WantAuthnRequestsSigned' field is set to false and KeyDescriptor lacks a usage attribute. Inspect SAML responses for missing signature validation in broker endpoints. Use network monitoring to detect unsigned SAML responses being accepted.

Impact Analysis

An attacker could exploit this to bypass authentication, impersonate any federated user, and access or modify their data. The attack requires knowing the target user's external SAML identifier and capturing a valid RelayState and SAML request ID during a login flow. Successful exploitation grants full account access without authentication.

Compliance Impact

This vulnerability could lead to unauthorized access to user accounts, violating confidentiality and integrity requirements in GDPR and HIPAA. It may result in data breaches, unauthorized data access, or modification, leading to potential non-compliance with these regulations' security and privacy controls.

Mitigation Strategies

Upgrade Keycloak to a patched version if available. Temporarily disable SAML authentication until patched. Review and update SAML metadata import configurations to ensure proper signature validation settings. Monitor for unauthorized access attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-16443. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart