CVE-2026-102471 CRLF header injection in vertx-mail-client allows manipulation of outgoing SMTP messages
- Published
- Updated
- Exploit status
- No public exploit known
Description
In Eclipse Vert.x versions [4.0.0, 4.5.34] or [5.0.0,5.0.12] or [5.1.0,5.1.9] or [5.2.0, 5.2.0], the vertx-mail-client does not sanitize CR (\r) or LF (\n) characters in user-supplied email header names and values before writing them into the SMTP DATA section. A CR/LF sequence embedded in a name or value passed to MailMessage.addHeader(), MailMessage.setHeaders(), MailAttachment.addHeader(), or MailAttachment.setHeaders() is written verbatim to the wire, allowing an attacker to inject arbitrary headers (e.g. Bcc, Reply-To, Content-Type) or prepend body content to the outgoing message.
The same weakness affects MIME part metadata set via MailAttachment.setContentType(), setDisposition(), setDescription(), and setContentId(), which are written directly into MIME part headers without validation.
A secondary weakness in Utils.mustEncode(char) additionally allows a bare LF in a From display-name to bypass Q-encoding and reach the wire unchanged.
An unauthenticated attacker who can control any header name, header value, or attachment metadata field passed to the mail client (for example via a web form or API that feeds into MailMessage) can exploit this to redirect email copies, spoof headers, or tamper with message structure.
The impacted component is io.vertx:vertx-mail-client.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| Eclipse Foundation Eclipse Vert.x | >= 4.0.0, <= 4.5.34 | No fix listed |
| Eclipse Foundation Eclipse Vert.x | >= 5.0.0, <= 5.0.12 | No fix listed |
| Eclipse Foundation Eclipse Vert.x | >= 5.1.0, <= 5.1.9 | No fix listed |
| Eclipse Foundation Eclipse Vert.x | = 5.2.0 | No fix listed |
| redhat/vertx-mail-client(Red Hat:quarkus:3) | All versions | No fix listed |
| eclipse vert.x | >= 4.5.0, < 4.5.35 | 4.5.35 |
| eclipse vert.x | >= 5.0.0, < 5.1.10 | 5.1.10 |
| eclipse vert.x | = 5.2.0 | No fix listed |
References
- github.com vendor-advisory
- gitlab.eclipse.org issue-tracking third-party-advisory
- Red Hat CVE page mitigation vendor-advisory
- Red Hat Bugzilla 2552815 issue-tracking
- www.cve.org
- nvd.nist.gov