# CVE-2025-8419: Org.keycloak/keycloak-services: keycloak smtp inject vulnerability

> Attackers can inject SMTP commands via email registration fields to send unsolicited short emails from the Keycloak server.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Aug 2025
- **Updated:** 31 Aug 2026
- **Also known as:** ECHO-891d-8502-3521, GHSA-m4j5-5x4r-2xp9, MINI-93mx-gh4v-7rhf

## What is CVE-2025-8419?

CVE-2025-8419 is a medium-severity vulnerability in Redhat Keycloak, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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

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.2.8 |
| `org.keycloak:keycloak-services` | Maven | All versions | 26.2.8 |
| `org.keycloak:keycloak-services` | Maven | From 26.3.0 | 26.3.3 |
| `org.keycloak:keycloak-services` | Maven | From 26.3.0 | 26.3.3 |

Products: Redhat Keycloak.

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

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

## Is CVE-2025-8419 being exploited?

There is no known exploitation of CVE-2025-8419 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-8419 and fix it if it is affected.

What it is: CVE-2025-8419 is a medium-severity vulnerability in Redhat Keycloak, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8419 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.2.8
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.2.8
- org.keycloak:keycloak-services (Maven): affected from 26.3.0; fixed in 26.3.3
- org.keycloak:keycloak-services (Maven): affected from 26.3.0; fixed in 26.3.3

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-8419/ (Markdown: https://insights.sbomify.com/CVE-2025-8419/index.md)
```

## Sources

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

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