Overview 206 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
199
96.6%
blocked by ARMR today
5
2.4%
partly blocked
0
0.0%
not blocked
201
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
201
97.6%
split by
peak 63 / quarter
Q2 253
No exploit published3
High1
Medium1
Low1
not blocked3
No public exploit3
Q3 255
No exploit published5
High1
Medium4
not blocked5
No public exploit5
Q4 259
Protected by Waratek1
No exploit published8
High1
Medium6
Low2
blocked by ARMR today1
not blocked8
No public exploit9
Q1 2630
Mitigation candidate1
No exploit published29
Critical1
High7
Medium11
Low11
not blocked30
Proof of concept only3
No public exploit27
Q2 2645
Protected by Waratek1
No exploit published44
High17
Medium27
Low1
blocked by ARMR today1
not blocked44
Proof of concept only1
No public exploit44
Q3 2663
Protected by Waratek2
Mitigation candidate1
No exploit published60
Critical5
High12
Medium44
Low2
blocked by ARMR today2
not blocked61
Exploited1
No public exploit62
Q4 2651
Protected by Waratek1
No exploit published50
Critical2
High13
Medium35
Low1
blocked by ARMR today1
not blocked50
No public exploit51
Q2 25Q3 25Q4 25Q1 26Q2 26Q3 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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. |
| CVE-2025-3910 | Medium | 2025-04-29 | No exploit published | No public exploit | A flaw was found in Keycloak. The org.keycloak.authorization package may be vulnerable to circumventing required actions, allowing users to circumvent requirements such as setting up two-factor authentication. |
| CVE-2025-3501 | High | 2025-04-29 | No exploit published | No public exploit | A flaw was found in Keycloak. By setting a verification policy to 'ALL', the trust store certificate verification is skipped, which is unintended. |