CVE-2025-7365
highpriority · track · 0EPSS 0.003 · 20 %ileDEEUUSEPSS · scored 2026-10-28
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 5.4–7.1
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (10)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2025-1512Keycloak: Kontoübernahme durch Manipulation des E-Mail-VerifizierungsprozessesDeutsch2025-07-08csaf · cert_bundDE
Ein entfernter authentisierter Angreifer kann eine Schwachstelle in Keycloak ausnutzen, um den Anmeldevorgang zu manipulieren und das Konto eines Opfers zu übernehmen.
- GHSA-xhpr-465j-7p9qKeycloak phishing attack via email verification step in first login flow2025-07-30ghsa · osvUS
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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (25)
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2025:11986cnnvd
- https://access.redhat.com/errata/RHSA-2025:11987cnnvd
- https://access.redhat.com/errata/RHSA-2025:12015cnnvd
- https://access.redhat.com/errata/RHSA-2025:12016cnnvd
- https://access.redhat.com/security/cve/CVE-2025-7365cnnvd
- https://bugzilla.redhat.com/show_bug.cgi?id=2378852cnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2025-7365cnnvd
- https://vigilance.fr/vulnerability/Keycloak-user-access-via-account-merging-47812cnnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan