Stack-memory disclosure via incomplete Proxy Protocol header
Published Sep 19, 2026 · Updated Sep 19, 2026
Information disclosure in Exim 4.83 through 4.100 allows remote attackers to read stack data through Proxy Protocol v2. Its Proxy Protocol v2 parser uses an incomplete header's uninitialized length field instead of repeating reads until the full header arrives. Exposure requires Proxy Protocol support, a hosts_proxy configuration, and a buggy or compromised configured proxy; leaked process memory is transmitted remotely.
Summary
What happened
Information disclosure in Exim 4.83 through 4.100 allows remote attackers to read stack data through Proxy Protocol v2. Its Proxy Protocol v2 parser uses an incomplete header's uninitialized length field instead of repeating reads until the full header arrives. Exposure requires Proxy Protocol support, a hosts_proxy configuration, and a buggy or compromised configured proxy; leaked process memory is transmitted remotely.
The record
- CVE
- CVE-2026-94056
- Published
- Sep 19, 2026
- Updated
- Sep 19, 2026
- Vendor
- LibSPF2 Project
- Product
- Exim
- Classifications
- CWE-908, 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=4.83 <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