Exim 4.88 before 4.99.4, in some proxy configurations, mishandles certain short payloads, leading to disclosure of uninitialized stack memory values to a client.
CVE-2026-48840
Score 5.3 from GitHub Security Advisory published 2026-05-30. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
May 30, 2026
Last Modified
July 22, 2026
Advisory Details (4)
Auto-updated Jun 16, 2026[SECURITY] [DLA 4615-1] exim4 security update
https://lists.debian.org/debian-lts-announce/2026/06/msg00004.htmloss-security - CVE-2026-48840: Exim 4.99.4: PROXY-protocol uninitialised-stack information disclosure
http://www.openwall.com/lists/oss-security/2026/05/29/3oss-security - CVE-2026-48840: Exim 4.99.4: PROXY-protocol uninitialised-stack information disclosure
https://www.openwall.com/lists/oss-security/2026/05/29/3Index of /static/doc/security/EXIM-Security-2026-05-19.1/
https://exim.org/static/doc/security/EXIM-Security-2026-05-19.1Vendor Advisories for CVE-2026-48840(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | eximon4 (4.99.1-1ubuntu1.3) @ resolute | 2026-08-25 | ubuntu |
| ubuntu | eximon4 (4.86.2-2ubuntu2.6+esm9) @ xenial | 2026-08-25 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| exim4 | 4.94.2-7 ... 4.94.2-7+deb11u5 (6 versions) | 4.94.2-7+deb11u6 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| exim4 | 4.96-15 ... 4.96-15+deb12u9 (10 versions) | 4.96-15+deb12u10 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| exim4 | 4.98.2-1, 4.98.2-1+deb13u1, 4.98.2-1+deb13u2 | 4.98.2-1+deb13u3 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| exim4 | 4.98.2-1 ... 4.99~RC3-2 (30 versions) | 4.99.3-2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(2)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 6× in last 7d / 69× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 235 total refreshes for this CVE.
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 04:08 UTCEG score recompute
- 2026-08-25 04:08 UTCVendor advisory
- 2026-08-25 04:08 UTCGHSA enrichment
- 2026-08-23 14:03 UTCEG score recompute
- 2026-08-23 14:03 UTCVendor advisory
- 2026-08-23 14:03 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 14:59 UTCEG score recompute
- 2026-08-21 14:59 UTCVendor advisory
- 2026-08-21 14:59 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 10:23 UTCEG score recompute
- 2026-08-20 10:23 UTCVendor advisory
- 2026-08-20 10:23 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 06:50 UTCEG score recompute
- 2026-08-17 06:50 UTCVendor advisory
- 2026-08-17 06:50 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:23 UTCEG score recompute
- 2026-08-16 02:23 UTCVendor advisory
- 2026-08-16 02:23 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-15 01:28 UTCVendor advisory
- 2026-08-15 01:28 UTCGHSA enrichment
- 2026-08-14 01:17 UTCEG score recompute
- 2026-08-14 01:17 UTCVendor advisory
- 2026-08-14 01:17 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 01:05 UTCEG score recompute
- 2026-08-13 01:05 UTCVendor advisory
- 2026-08-13 01:05 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 00:54 UTCEG score recompute
- 2026-08-12 00:54 UTCVendor advisory
- 2026-08-12 00:54 UTCGHSA enrichment
- 2026-08-11 00:43 UTCEG score recompute
- 2026-08-11 00:43 UTCVendor advisory
- 2026-08-11 00:43 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 00:31 UTCEG score recompute
- 2026-08-10 00:31 UTCVendor advisory
- 2026-08-10 00:31 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 00:20 UTCEG score recompute
- 2026-08-09 00:20 UTCVendor advisory
- 2026-08-09 00:20 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 00:08 UTCEG score recompute
- 2026-08-08 00:08 UTCVendor advisory
- 2026-08-08 00:08 UTCGHSA enrichment
- 2026-08-06 23:57 UTCEG score recompute
- 2026-08-06 23:57 UTCVendor advisory
- 2026-08-06 23:56 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 23:10 UTCEG score recompute
- 2026-08-05 23:10 UTCVendor advisory
- 2026-08-05 23:10 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 22:58 UTCEG score recompute
- 2026-08-04 22:58 UTCVendor advisory
- 2026-08-04 22:58 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 15:54 UTCVendor advisory
- 2026-08-03 15:54 UTCGHSA enrichment
- 2026-08-02 14:04 UTCEG score recompute
- 2026-08-02 14:04 UTCVendor advisory
- 2026-08-02 14:04 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 13:53 UTCEG score recompute
- 2026-08-01 13:53 UTCVendor advisory
- 2026-08-01 13:53 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 05:50 UTCEG score recompute
- 2026-07-31 05:50 UTCVendor advisory
- 2026-07-31 05:50 UTCGHSA enrichment
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 11:32 UTCEG score recompute
- 2026-07-29 11:31 UTCGHSA enrichment
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 04:01 UTCEG score recompute
- 2026-07-28 04:00 UTCGHSA enrichment
- 2026-07-27 03:07 UTCEG score recompute
- 2026-07-27 03:07 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-48840?
When was CVE-2026-48840 disclosed?
Is CVE-2026-48840 actively exploited?
What is the CVSS score of CVE-2026-48840?
How do I remediate CVE-2026-48840?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48840
Is Your Infrastructure Affected by CVE-2026-48840?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.