Skip to content

Keycloak phishing attack via email verification step in first login flow

Moderate severity GitHub Reviewed Published Jul 29, 2025 in keycloak/keycloak • Updated Jul 30, 2025

Package

maven org.keycloak:keycloak-services (Maven)

Affected versions

< 26.0.13
>= 26.2.0, < 26.2.6

Patched versions

26.0.13
26.2.6

Description

There is a flaw with the first login flow where, during a IdP login, an attacker with a registered account can initiate the process to merge accounts with an existing victim's account. The attacker will subsequently be prompted to "review profile" information, which allows the the attacker to modify their email address to that of a victim's account. This triggers a verification email sent to the victim's email address. If the victim clicks the verification link, the attacker can gain access to the victim's account. While not a zero-interaction attack, the attacker's email address is not directly present in the verification email content, making it a potential phishing opportunity.

This issue has been fixed in versions 26.0.13, 26.2.6, and 26.3.0.

References

@rmartinc rmartinc published to keycloak/keycloak Jul 29, 2025
Published to the GitHub Advisory Database Jul 30, 2025
Reviewed Jul 30, 2025
Last updated Jul 30, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(13th percentile)

Weaknesses

Origin Validation Error

The product does not properly verify that the source of data or communication is valid. Learn more on MITRE.

CVE ID

CVE-2025-7365

GHSA ID

GHSA-xhpr-465j-7p9q

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.