Unsolicited email via Unicode-to-CRLF SMTP injection
Published Aug 6, 2025 · Updated Aug 31, 2026
SMTP injection in Keycloak before 26.3.3 allows remote attackers to send a short unsolicited email through its configured SMTP server. Email-registration recipient handling passes a crafted Unicode local part whose low bytes form CRLF-delimited SMTP commands. The unauthenticated path requires registration and outbound SMTP; the 64-character local-part limit restricts the injected subject and body.
Summary
What happened
SMTP injection in Keycloak before 26.3.3 allows remote attackers to send a short unsolicited email through its configured SMTP server. Email-registration recipient handling passes a crafted Unicode local part whose low bytes form CRLF-delimited SMTP commands. The unauthenticated path requires registration and outbound SMTP; the 64-character local-part limit restricts the injected subject and body.
The record
- CVE
- CVE-2025-8419
- Published
- Aug 6, 2025
- Updated
- Aug 31, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-20, CWE-93
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2025CVE publishedPublication date reported by the CVE source.
- Aug 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo