CVE-2026-102471
MEDIUMDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 23% of all known CVEs.
References
Related Vulnerabilities
Other CWE-93 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-61884 | High | 7.5 | 96% | KEV + Ransom | - |
| CVE-2022-0666 | High | 7.5 | 44% | - | Fix |
| CVE-2016-3115 | Medium | 6.4 | 36% | - | Fix |
| CVE-2024-20337 | High | 8.2 | 30% | - | Fix |
| CVE-2021-39172 | High | 8.8 | 29% | - | Fix |
| CVE-2016-4975 | Medium | 6.1 | 20% | - | Fix |
Common questions
How do I fix CVE-2026-102471?
Upgrade vert.x to 5.1.10 or later.
Is CVE-2026-102471 being actively exploited?
Not that we know of. CVE-2026-102471 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.31% is the estimated probability that it will be exploited in the next 30 days. That is higher than 23% of all scored CVEs.
How severe is CVE-2026-102471?
CVE-2026-102471 has a CVSS v3 base score of 5.9, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-102471 affect?
Published advisories record a fix for vert.x (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-102471
Markdown
[](https://tridentstack.com/cve/CVE-2026-102471)HTML
<a href="https://tridentstack.com/cve/CVE-2026-102471"><img src="https://tridentstack.com/cve/badge/CVE-2026-102471.svg" alt="CVE-2026-102471"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-20.