Red Hat Security Advisory: Red Hat build of Keycloak 26.4.13 Images Security Update
Red Hat build of Keycloak is an integrated sign-on solution, available as a Red Hat JBoss Middleware for OpenShift containerized image. The Red Hat build of Keycloak for OpenShift image provides an authentication server that you can use to log in centrally, log out, and register. You can also manage user accounts for web applications, mobile applications, and RESTful web services. Red Hat build of Keycloak Operator for OpenShift simplifies deployment and management of Keycloak 26.4.13 clusters. This erratum releases new images for Red Hat build of Keycloak 26.4.13 for use within the OpenShift Container Platform cloud computing Platform-as-a-Service (PaaS) for on-premise or private cloud deployments, aligning with the standalone product release. Security fixes: * Information disclosure via CORS header injection due to unvalidated JWT azp claim (CVE-2026-37977) * Server-Side Request Forgery via OIDC token endpoint manipulation (CVE-2026-4874) * eclipse-vertx/vert.x:Denial of Service via TLS handshake with wildcard server name (CVE-2026-6860) * Improper Access Control on Keycloak Server when the account Account API feature is disabled (CVE-2026-7500) * Policy bypass during WebAuthn credential registration via client-side JavaScript manipulation (CVE-2026-8830) * Security flaw in org.keycloak/keycloak-services (CVE-2026-8922) * Information disclosure through arbitrary filesystem path probing (CVE-2026-9083) * Cross-site scripting (XSS) via case-insensitive URI validation bypass (CVE-2026-9086) * Cross-Session Email Verification Proof Not Bound to Upstream Identity in First-Broker-Login (CVE-2026-9087) * Information disclosure due to user profile permission bypass (CVE-2026-9088) * Group-Admin Escalation to Realm-Admin (CVE-2026-9099) * Privilege escalation due to oversized subject_token JWT (CVE-2026-9704) * Attacker can re-enable and take over disabled clients via Registration Access Token (CVE-2026-9705) * Organization Data Leak After Feature Disabled in Keycloak (CVE-2026-9791) * Security restriction bypass allows unauthorized ROPC token acquisition (CVE-2026-9792) * Information disclosure via SAML ECP endpoint (CVE-2026-9794) * Privilege escalation via improper scope mapping enforcement (CVE-2026-9795) * Unauthorized access to resources via UMA permission ticket bypass (CVE-2026-9799) * Authorization bypass via incorrect URI comparison (CVE-2026-9800) * Denial of Service via malformed LDAP password policy response (CVE-2026-9801) * Unauthorized account access via replayed refresh tokens after cluster restart (CVE-2026-9802) * Denial of Service via malformed Authorization header (CVE-2026-9803)
AI Analysis
Technical Summary
The Red Hat build of Keycloak 26.4.13 contains multiple security vulnerabilities affecting authentication, authorization, and session management components. Notable issues include information disclosure via CORS header injection (CVE-2026-37977), server-side request forgery via OIDC token endpoint manipulation (CVE-2026-4874), denial of service via TLS handshake (CVE-2026-6860), improper access control when the account API is disabled (CVE-2026-7500), policy bypass during WebAuthn registration (CVE-2026-8830), privilege escalation via oversized JWT tokens (CVE-2026-9704), and multiple authorization bypasses and information disclosures. These vulnerabilities impact the security posture of Keycloak deployments used for centralized authentication and single sign-on in OpenShift environments. Red Hat has released updated container images and packages to address these issues.
Potential Impact
Successful exploitation of these vulnerabilities could lead to unauthorized information disclosure, privilege escalation, denial of service conditions, bypass of authentication and authorization controls, and unauthorized access to protected resources. This could compromise the confidentiality, integrity, and availability of authentication services and user data managed by Keycloak in affected deployments.
Mitigation Recommendations
Red Hat has released updated images and packages for the Red Hat build of Keycloak 26.4.13 and 26.6.3 that address these vulnerabilities. Users should apply these updates promptly. Before updating, it is recommended to back up existing installations, including applications, configuration files, and databases. No vendor advisory indicates that no action is required or that these issues are already mitigated. Therefore, applying the official patches is the recommended remediation.
Red Hat Security Advisory: Red Hat build of Keycloak 26.4.13 Images Security Update
Description
Red Hat build of Keycloak is an integrated sign-on solution, available as a Red Hat JBoss Middleware for OpenShift containerized image. The Red Hat build of Keycloak for OpenShift image provides an authentication server that you can use to log in centrally, log out, and register. You can also manage user accounts for web applications, mobile applications, and RESTful web services. Red Hat build of Keycloak Operator for OpenShift simplifies deployment and management of Keycloak 26.4.13 clusters. This erratum releases new images for Red Hat build of Keycloak 26.4.13 for use within the OpenShift Container Platform cloud computing Platform-as-a-Service (PaaS) for on-premise or private cloud deployments, aligning with the standalone product release. Security fixes: * Information disclosure via CORS header injection due to unvalidated JWT azp claim (CVE-2026-37977) * Server-Side Request Forgery via OIDC token endpoint manipulation (CVE-2026-4874) * eclipse-vertx/vert.x:Denial of Service via TLS handshake with wildcard server name (CVE-2026-6860) * Improper Access Control on Keycloak Server when the account Account API feature is disabled (CVE-2026-7500) * Policy bypass during WebAuthn credential registration via client-side JavaScript manipulation (CVE-2026-8830) * Security flaw in org.keycloak/keycloak-services (CVE-2026-8922) * Information disclosure through arbitrary filesystem path probing (CVE-2026-9083) * Cross-site scripting (XSS) via case-insensitive URI validation bypass (CVE-2026-9086) * Cross-Session Email Verification Proof Not Bound to Upstream Identity in First-Broker-Login (CVE-2026-9087) * Information disclosure due to user profile permission bypass (CVE-2026-9088) * Group-Admin Escalation to Realm-Admin (CVE-2026-9099) * Privilege escalation due to oversized subject_token JWT (CVE-2026-9704) * Attacker can re-enable and take over disabled clients via Registration Access Token (CVE-2026-9705) * Organization Data Leak After Feature Disabled in Keycloak (CVE-2026-9791) * Security restriction bypass allows unauthorized ROPC token acquisition (CVE-2026-9792) * Information disclosure via SAML ECP endpoint (CVE-2026-9794) * Privilege escalation via improper scope mapping enforcement (CVE-2026-9795) * Unauthorized access to resources via UMA permission ticket bypass (CVE-2026-9799) * Authorization bypass via incorrect URI comparison (CVE-2026-9800) * Denial of Service via malformed LDAP password policy response (CVE-2026-9801) * Unauthorized account access via replayed refresh tokens after cluster restart (CVE-2026-9802) * Denial of Service via malformed Authorization header (CVE-2026-9803)
Affected software
pkg:github/keycloak/keycloakRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Red Hat build of Keycloak 26.4.13 contains multiple security vulnerabilities affecting authentication, authorization, and session management components. Notable issues include information disclosure via CORS header injection (CVE-2026-37977), server-side request forgery via OIDC token endpoint manipulation (CVE-2026-4874), denial of service via TLS handshake (CVE-2026-6860), improper access control when the account API is disabled (CVE-2026-7500), policy bypass during WebAuthn registration (CVE-2026-8830), privilege escalation via oversized JWT tokens (CVE-2026-9704), and multiple authorization bypasses and information disclosures. These vulnerabilities impact the security posture of Keycloak deployments used for centralized authentication and single sign-on in OpenShift environments. Red Hat has released updated container images and packages to address these issues.
Potential Impact
Successful exploitation of these vulnerabilities could lead to unauthorized information disclosure, privilege escalation, denial of service conditions, bypass of authentication and authorization controls, and unauthorized access to protected resources. This could compromise the confidentiality, integrity, and availability of authentication services and user data managed by Keycloak in affected deployments.
Mitigation Recommendations
Red Hat has released updated images and packages for the Red Hat build of Keycloak 26.4.13 and 26.6.3 that address these vulnerabilities. Users should apply these updates promptly. Before updating, it is recommended to back up existing installations, including applications, configuration files, and databases. No vendor advisory indicates that no action is required or that these issues are already mitigated. Therefore, applying the official patches is the recommended remediation.
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:25097
- Cve Count
- 14
- Additional Cves
- ["CVE-2026-7500","CVE-2026-8830","CVE-2026-8922","CVE-2026-9087","CVE-2026-9088","CVE-2026-9704","CVE-2026-9791","CVE-2026-9792","CVE-2026-9794","CVE-2026-9801","CVE-2026-9802","CVE-2026-9803","CVE-2026-37977"]
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a2a7b4d9e049e7b7ee8d6b6
Added to database: 06/11/2026, 09:09:33 UTC
Last enriched: 08/10/2026, 20:04:00 UTC
Last updated: 09/14/2026, 22:01:35 UTC
Views: 1529
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.
External Links
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.