Message integrity loss via rejected DATA mishandling
Published Sep 19, 2026 · Updated Sep 19, 2026
SMTP smuggling in Exim 4.100 and earlier allows remote attackers to alter received message content via crafted post-rejection DATA. The SMTP reception path misidentifies the end of a rejected DATA phase and processes attacker-supplied trailing bytes as a different message. Exploitation requires a DATA-phase rejection; normal receive processing still applies to the smuggled message, limiting the result to message-integrity loss.
Summary
What happened
SMTP smuggling in Exim 4.100 and earlier allows remote attackers to alter received message content via crafted post-rejection DATA. The SMTP reception path misidentifies the end of a rejected DATA phase and processes attacker-supplied trailing bytes as a different message. Exploitation requires a DATA-phase rejection; normal receive processing still applies to the smuggled message, limiting the result to message-integrity loss.
The record
- CVE
- CVE-2026-94057
- Published
- Sep 19, 2026
- Updated
- Sep 19, 2026
- Vendor
- LibSPF2 Project
- Product
- Exim
- Classifications
- CWE-93, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 2026CVE publishedPublication date reported by the CVE source.
- Sep 19, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.100.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started