WaratekVRT Sign in
Reset
More filters (2)
Columns
Description: Keycloak✕Published from 2025-10-01✕
Overview 204 matches · 5 protected · 1 exploited · 0 CISA KEV · 2 public PoC · 0 EPSS ≥ 0.5
204matches 5protected2.5% 1exploited0.5% 0CISA KEV0.0% 2public PoC1.0% 0EPSS ≥ 0.50.0%
split by peak 38 / month
No exploit published: 197Mitigation candidate: 2Protected by Waratek: 5 Low: 17Medium: 129High: 50Critical: 8 not blocked: 199blocked by ARMR today: 5 No public exploit: 199Proof of concept only: 4Exploited: 1
Nov 25Jan 26Mar 26May 26Jul 26Sep 26Nov 26
204 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed. ‹ prev page 3 of 3 next ›
CVE Severity Published▾ Status Exploitation Description
CVE-2025-12390 Medium 2025-10-28 No exploit published No public exploit A flaw was found in Keycloak. In Keycloak where a user can accidentally get access to another user's session if both use the same device and browser. This happens because Keycloak sometimes reuses session identifiers and doesn’t clean up properly during logout when browser cookies are missing. As a result, one user may receive tokens that belong to another user.
CVE-2025-10939 Low 2025-10-28 No exploit published No public exploit A flaw was found in Keycloak. The Keycloak guides recommend to not expose /admin path to the outside in case the installation is using a proxy. The issue occurs at least via ha-proxy, as it can be tricked to using relative/non-normalized paths to access the /admin application path relative to /realms which is expected to be exposed.
CVE-2025-12110 Medium 2025-10-23 No exploit published No public exploit A flaw was found in Keycloak. An offline session continues to be valid when the offline_access scope is removed from the client. The refresh token is accepted and you can continue to request new tokens for the session. As it can lead to a situation where an administrator removes the scope, and assumes that offline sessions are no longer available, but they are.
CVE-2025-11429 Medium 2025-10-23 No exploit published No public exploit A flaw was found in Keycloak. Keycloak does not immediately enforce the disabling of the "Remember Me" realm setting on existing user sessions. Sessions created while "Remember Me" was active retain their extended session lifetime until they expire, overriding the administrator's recent security configuration change. This is a logic flaw in session management increases the potential window for successful session hijacking or unauthorized long-term access persistence. The flaw lies in the session expiration logic relying on the session-local "remember-me" flag without validating the current realm-level configuration.
‹ prev page 3 of 3 next ›