Skip to content
Fencer Intel
medium 5.3

CVE-2025-8419 json

Org.keycloak/keycloak-services: keycloak smtp inject vulnerability

published last yr. modified 2mo ago also GHSA-m4j5-5x4r-2xp9 , EUVD-2025-23863

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.keycloak:keycloak-services 26.2.8, 26.3.3
  • Keycloak keycloak 26.3.3
  • Red Hat Red Hat build of Keycloak 26.0 26.0-18, 26.0-19, 26.0.15-1
  • Red Hat Red Hat build of Keycloak 26.2 26.2-8, 26.2.8-1

Is CVE-2025-8419 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-8419 updated cvss 5.3

org.keycloak/keycloak-services: Keycloak SMTP Inject Vulnerability

  • Red Hat Build of Keycloak keycloak-services
    affected: workaround, no fix planned “Currently, no mitigation is available for this vulnerability.”
  • Red Hat build of Keycloak 26.0 rhbk/keycloak-rhel9 26.0-18, rhbk/keycloak-rhel9-operator 26.0-19, rhbk/keycloak-operator-bundle 26.0.15-1
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHSA-2025:15337
  • Red Hat build of Keycloak 26.2 rhbk/keycloak-rhel9 26.2-8, rhbk/keycloak-rhel9-operator 26.2-8, rhbk/keycloak-operator-bundle 26.2.8-1
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHSA-2025:15338

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.62% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-services
<26.2.8
>=26.3.0, <26.3.3
26.2.8
26.3.3

Affected products

  • Keycloak keycloak
  • Red Hat Red Hat build of Keycloak 26.0
  • Red Hat Red Hat build of Keycloak 26.2
  • Red Hat Red Hat Build of Keycloak

Classification

Weakness
  • CWE-93 Improper Neutralization of CRLF Sequences

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.