Threats Tagged 'cve-2026-16093'
View all threats tagged with 'cve-2026-16093'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-16093'
Click on any threat for detailed analysis and mitigation recommendations
Red Hat has released a security update for the Red Hat build of Keycloak 26.6.7 images used in OpenShift Container Platform. This update addresses multiple security vulnerabilities including information disclosure, privilege escalation, authorization bypasses, remote code execution, and denial of service issues. The update provides new container images that align with the standalone Keycloak product release. Users of Red Hat build of Keycloak 26.6.7 are advised to apply the update to mitigate these risks. Join the discussion | GCVE Database | 09/16/2026, 15:46:54 UTC Added: 09/29/2026, 21:04:20 UTC |
Red Hat has released a security update for Red Hat build of Keycloak 26.6.7 addressing multiple vulnerabilities. These include issues such as information disclosure, privilege escalation, authorization bypasses, remote code execution, and denial of service. The update fixes a wide range of security flaws affecting authentication, authorization, token handling, and endpoint protections. Users of affected versions are advised to apply the update to mitigate these risks. Join the discussion | GCVE Database | 09/16/2026, 15:45:17 UTC Added: 09/29/2026, 21:04:20 UTC |
0 Keycloak provides a mechanism called Client Policies to enforce security requirements on clients, such as requiring them to use signed JWTs for authentication. A flaw was discovered where this enforcement can be bypassed. An attacker with valid client credentials can provide a fake, unsigned assertion header that tricks the system into thinking the policy requirements have been met. This allows the attacker to authenticate using simpler methods like a client secret even when the administrator has mandated more secure, signed assertions. Join the discussion | CVE Database V5 | 07/17/2026, 16:42:52 UTC Added: 07/18/2026, 11:08:42 UTC |
Showing 1 to 3 of 3 results