# CVE-2025-7365: Keycloak: phishing attack via email verification step in first login flow

> Attackers can hijack victim accounts by manipulating email verification links during identity provider account merging flows.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Jul 2025
- **Updated:** 31 Aug 2026
- **Also known as:** ECHO-26f2-acde-46cc, GHSA-xhpr-465j-7p9q, MINI-gj5q-8ph8-5w5q

## What is CVE-2025-7365?

CVE-2025-7365 is a high-severity vulnerability in Redhat Keycloak, published on 10 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2025-7365?

4 open source packages ship an affected version, including org.keycloak:keycloak-services. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | All versions | 26.0.13 |
| `org.keycloak:keycloak-services` | Maven | All versions | 26.0.13 |
| `org.keycloak:keycloak-services` | Maven | From 26.2.0 | 26.2.6 |
| `org.keycloak:keycloak-services` | Maven | From 26.2.0 | 26.2.6 |

Products: Redhat Keycloak.

## How do I fix CVE-2025-7365?

Upgrade org.keycloak:keycloak-services to a fixed version for your release line: 26.0.13 or 26.2.6.

## Is CVE-2025-7365 being exploited?

There is no known exploitation of CVE-2025-7365 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Keycloak

- [CVE-2022-4361](https://insights.sbomify.com/CVE-2022-4361/): Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC (critical 10.0)
- [CVE-2022-1245](https://insights.sbomify.com/CVE-2022-1245/): Keycloak vulnerable to privilege escalation on Token Exchange feature (critical 9.8)
- [CVE-2021-20195](https://insights.sbomify.com/CVE-2021-20195/): keycloak Self Stored Cross-site Scripting vulnerability (critical 9.6)
- [CVE-2019-14910](https://insights.sbomify.com/CVE-2019-14910/): Keycloak Authentication Error (critical 9.3)
- [CVE-2019-14909](https://insights.sbomify.com/CVE-2019-14909/): Keycloak Authentication Error (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7365 and fix it if it is affected.

What it is: CVE-2025-7365 is a high-severity vulnerability in Redhat Keycloak, published on 10 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-7365 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.0.13
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.0.13
- org.keycloak:keycloak-services (Maven): affected from 26.2.0; fixed in 26.2.6
- org.keycloak:keycloak-services (Maven): affected from 26.2.0; fixed in 26.2.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-7365/ (Markdown: https://insights.sbomify.com/CVE-2025-7365/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7365
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7365
- OSV: https://osv.dev/vulnerability/CVE-2025-7365

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-7365/
Summaries are generated and may contain mistakes; the official description above is the record.