Red Hat Security Advisory: Red Hat build of Keycloak 26.4.10 Update
Red Hat build of Keycloak 26.4.10 is a standalone server, based on the Keycloak project, that provides authentication and standards-based single sign-on capabilities for web and mobile applications. Security fixes: * Keycloak SAML broker: Authentication bypass due to disabled SAML client completing IdP-initiated login (CVE-2026-3047) * Improper Enforcement of Disabled Identity Provider in IdentityBrokerService (Authentication Bypass) (CVE-2026-3009) * Unauthorized authentication via disabled SAML Identity Provider (CVE-2026-2603) * Unauthorized access via improper validation of encrypted SAML assertions (CVE-2026-2092) * Missing Check on Disabled Client for Docker Registry Protocol (CVE-2026-2733) * Denial of Service due to excessive SAMLRequest decompression (CVE-2026-2575) * Keycloak SAML brokering: Response delay due to unchecked NotOnOrAfter in SubjectConfirmationData (CVE-2026-1190) * Keycloak Authorization Header Parsing Leading to Potential Security Control Bypass (CVE-2026-0707)
AI Analysis
Technical Summary
The Red Hat build of Keycloak 26.4.10 contains multiple security vulnerabilities affecting authentication and authorization mechanisms. Notable issues include authentication bypasses due to disabled SAML clients and identity providers (CVE-2026-3047, CVE-2026-3009, CVE-2026-2603), improper validation of encrypted SAML assertions allowing unauthorized access (CVE-2026-2092), denial of service caused by excessive decompression of SAML requests (CVE-2026-2575), response delays due to unchecked NotOnOrAfter timestamps in SAML brokering (CVE-2026-1190), missing checks on disabled clients for Docker Registry protocol (CVE-2026-2733), and potential security control bypass via authorization header parsing (CVE-2026-0707). These vulnerabilities collectively impact the integrity and availability of authentication services provided by Keycloak.
Potential Impact
Successful exploitation of these vulnerabilities could allow attackers to bypass authentication controls, gain unauthorized access, cause denial of service conditions, or circumvent security controls in the affected Keycloak server. This could compromise the security of web and mobile applications relying on Keycloak for authentication and single sign-on.
Mitigation Recommendations
Red Hat has released an updated package for the Red Hat build of Keycloak version 26.4.10 that addresses these vulnerabilities. Users should back up their existing installations, including applications, configuration files, and databases, before applying the update. Applying this update is the recommended remediation. No additional mitigations are specified by the vendor advisory.
Red Hat Security Advisory: Red Hat build of Keycloak 26.4.10 Update
Description
Red Hat build of Keycloak 26.4.10 is a standalone server, based on the Keycloak project, that provides authentication and standards-based single sign-on capabilities for web and mobile applications. Security fixes: * Keycloak SAML broker: Authentication bypass due to disabled SAML client completing IdP-initiated login (CVE-2026-3047) * Improper Enforcement of Disabled Identity Provider in IdentityBrokerService (Authentication Bypass) (CVE-2026-3009) * Unauthorized authentication via disabled SAML Identity Provider (CVE-2026-2603) * Unauthorized access via improper validation of encrypted SAML assertions (CVE-2026-2092) * Missing Check on Disabled Client for Docker Registry Protocol (CVE-2026-2733) * Denial of Service due to excessive SAMLRequest decompression (CVE-2026-2575) * Keycloak SAML brokering: Response delay due to unchecked NotOnOrAfter in SubjectConfirmationData (CVE-2026-1190) * Keycloak Authorization Header Parsing Leading to Potential Security Control Bypass (CVE-2026-0707)
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Red Hat build of Keycloak 26.4.10 contains multiple security vulnerabilities affecting authentication and authorization mechanisms. Notable issues include authentication bypasses due to disabled SAML clients and identity providers (CVE-2026-3047, CVE-2026-3009, CVE-2026-2603), improper validation of encrypted SAML assertions allowing unauthorized access (CVE-2026-2092), denial of service caused by excessive decompression of SAML requests (CVE-2026-2575), response delays due to unchecked NotOnOrAfter timestamps in SAML brokering (CVE-2026-1190), missing checks on disabled clients for Docker Registry protocol (CVE-2026-2733), and potential security control bypass via authorization header parsing (CVE-2026-0707). These vulnerabilities collectively impact the integrity and availability of authentication services provided by Keycloak.
Potential Impact
Successful exploitation of these vulnerabilities could allow attackers to bypass authentication controls, gain unauthorized access, cause denial of service conditions, or circumvent security controls in the affected Keycloak server. This could compromise the security of web and mobile applications relying on Keycloak for authentication and single sign-on.
Mitigation Recommendations
Red Hat has released an updated package for the Red Hat build of Keycloak version 26.4.10 that addresses these vulnerabilities. Users should back up their existing installations, including applications, configuration files, and databases, before applying the update. Applying this update is the recommended remediation. No additional mitigations are specified by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_security_advisory
- Csaf Version
- 2.0
- Publisher
- Red Hat Product Security
- Advisory Id
- RHSA-2026:3947
- Cve Count
- 8
- Additional Cves
- ["CVE-2026-1190","CVE-2026-2092","CVE-2026-2575","CVE-2026-2603","CVE-2026-2733","CVE-2026-3009","CVE-2026-3047"]
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a273213e29bf47b509c0905
Added to database: 06/08/2026, 21:20:19 UTC
Last enriched: 08/17/2026, 18:20:34 UTC
Last updated: 09/12/2026, 10:01:29 UTC
Views: 114
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.