Connection-process crash and heap disclosure via SPA buffers
Published Apr 30, 2026 · Updated Apr 30, 2026
Memory corruption in Exim before 4.99.2 allows remote attackers to crash a connection process or read uninitialized heap data via SPA. The SPA decoder leaves its destination buffer uninitialized, while SPA field builders copy attacker-controlled data into fixed buffers without complete bounds enforcement. Exploitation requires the SPA driver and a hostile or compromised SPA/NTLM peer; impact is limited to the connection process and heap data exposed to that peer.
Summary
What happened
Memory corruption in Exim before 4.99.2 allows remote attackers to crash a connection process or read uninitialized heap data via SPA. The SPA decoder leaves its destination buffer uninitialized, while SPA field builders copy attacker-controlled data into fixed buffers without complete bounds enforcement. Exploitation requires the SPA driver and a hostile or compromised SPA/NTLM peer; impact is limited to the connection process and heap data exposed to that peer.
The record
- CVE
- CVE-2026-40687
- Published
- Apr 30, 2026
- Updated
- Apr 30, 2026
- Vendor
- LibSPF2 Project
- Product
- Exim
- Classifications
- CWE-909, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 30, 2026CVE publishedPublication date reported by the CVE source.
- Apr 30, 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.99.2
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