Overview 210 matches · 5 protected · 1 exploited · 0 CISA KEV · 2 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
5
2.4%
Rule in development
0
0.0%
Mitigation candidate
2
1.0%
No exploit published
203
96.7%
blocked by ARMR today
5
2.4%
partly blocked
0
0.0%
not blocked
205
97.6%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
0.5%
Working exploit published
0
0.0%
Proof of concept only
4
1.9%
Forecast only
0
0.0%
No public exploit
205
97.6%
split by
peak 38 / month
Jun 251
No exploit published1
Low1
not blocked1
No public exploit1
Jul 252
No exploit published2
High1
Medium1
not blocked2
No public exploit2
Aug 252
No exploit published2
Medium2
not blocked2
No public exploit2
Sep 251
No exploit published1
Medium1
not blocked1
No public exploit1
Oct 254
No exploit published4
Medium3
Low1
not blocked4
No public exploit4
Nov 252
Protected by Waratek1
No exploit published1
Medium2
blocked by ARMR today1
not blocked1
No public exploit2
Dec 253
No exploit published3
High1
Medium1
Low1
not blocked3
No public exploit3
Jan 267
No exploit published7
Medium3
Low4
not blocked7
No public exploit7
Feb 269
Mitigation candidate1
No exploit published8
Critical1
High2
Medium3
Low3
not blocked9
Proof of concept only2
No public exploit7
Mar 2614
No exploit published14
High5
Medium5
Low4
not blocked14
Proof of concept only1
No public exploit13
Apr 269
No exploit published9
High5
Medium4
not blocked9
Proof of concept only1
No public exploit8
May 2624
No exploit published24
High8
Medium16
not blocked24
No public exploit24
Jun 2612
Protected by Waratek1
No exploit published11
High4
Medium7
Low1
blocked by ARMR today1
not blocked11
No public exploit12
Jul 2630
No exploit published30
Critical2
High2
Medium25
Low1
not blocked30
No public exploit30
Aug 2617
Mitigation candidate1
No exploit published16
Critical3
High6
Medium7
Low1
not blocked17
Exploited1
No public exploit16
Sep 2616
Protected by Waratek2
No exploit published14
High4
Medium12
blocked by ARMR today2
not blocked14
No public exploit16
Oct 2619
Protected by Waratek1
No exploit published18
Medium19
blocked by ARMR today1
not blocked18
No public exploit19
Nov 2638
No exploit published38
Critical2
High13
Medium22
Low1
not blocked38
No public exploit38
Jul 25Sep 25Nov 25Jan 26Mar 26May 26Jul 26Sep 26Nov 26
| 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. |
| CVE-2025-10044 | Medium | 2025-09-05 | No exploit published | No public exploit | A flaw was found in Keycloak. Keycloak’s account console and other pages accept arbitrary text in the error_description query parameter. This text is directly rendered in error pages without validation or sanitization. While HTML encoding prevents XSS, an attacker can craft URLs with misleading messages (e.g., fake support phone numbers or URLs), which are displayed within the trusted Keycloak UI. This creates a phishing vector, potentially tricking users into contacting malicious actors. |
| CVE-2025-9162 | Medium | 2025-08-21 | No exploit published | No public exploit | A flaw was found in org.keycloak/keycloak-model-storage-service. The KeycloakRealmImport custom resource substitutes placeholders within imported realm documents, potentially referencing environment variables. This substitution process allows for injection attacks when crafted realm documents are processed. An attacker can leverage this to inject malicious content during the realm import procedure. This can lead to unintended consequences within the Keycloak environment. |
| CVE-2025-8419 | Medium | 2025-08-06 | No exploit published | No public exploit | A vulnerability was found in Keycloak-services. Special characters used during e-mail registration may perform SMTP Injection and unexpectedly send short unwanted e-mails. The email is limited to 64 characters (limited local part of the email), so the attack is limited to very shorts emails (subject and little data, the example is 60 chars). This flaw's only direct consequence is an unsolicited email being sent from the Keycloak server. However, this action could be a precursor for more sophisticated attacks. |
| CVE-2025-7784 | Medium | 2025-07-18 | No exploit published | No public exploit | A flaw was found in the Keycloak identity and access management system when Fine-Grained Admin Permissions(FGAPv2) are enabled. An administrative user with the manage-users role can escalate their privileges to realm-admin due to improper privilege enforcement. This vulnerability allows unauthorized elevation of access rights, compromising the intended separation of administrative duties and posing a security risk to the realm. |
| CVE-2025-7365 | High | 2025-07-10 | No exploit published | No public exploit | A flaw was found in Keycloak. When an authenticated attacker attempts to merge accounts with another existing account during an identity provider (IdP) login, the attacker will subsequently be prompted to "review profile" information. This vulnerability allows the attacker to modify their email address to match that of a victim's account, triggering a verification email sent to the victim's email address. The attacker's email address is not present in the verification email content, making it a potential phishing opportunity. If the victim clicks the verification link, the attacker can gain access to the victim's account. |
| CVE-2025-5416 | Low | 2025-06-20 | No exploit published | No public exploit | A vulnerability has been identified in Keycloak that could lead to unauthorized information disclosure. While it requires an already authenticated user, the /admin/serverinfo endpoint can inadvertently provide sensitive environment information. |