Exim before 4.99.3, in certain GnuTLS configurations, has a remotely reachable use-after-free in the BDAT body parsing path. It is triggered when a client sends a TLS close_notify mid-body during a CHUNKING transfer, followed by a final cleartext byte on the same TCP connection. This can lead to heap corruption. An unauthenticated network attacker exploiting this vulnerability could execute arbitrary code.
CVE-2026-45185
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-12. NVD baseline CVSS 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EPSS
- 65.4%
- KEV
- Not listed
Published
May 12, 2026
Last Modified
May 28, 2026
Advisory Details (7)
Auto-updated Jun 20, 2026oss-security - Re: [EXIM-Security-2026-05-01.1] Security Release 4.99.3
http://www.openwall.com/lists/oss-security/2026/05/12/25XBOW - Dead.Letter (CVE-2026-45185) How XBOW Found an Unauthenticated RCE on Exim
https://xbow.com/blog/dead-letter-cve-2026-45185-xbow-found-rce-eximoss-security - [EXIM-Security-2026-05-01.1] Security Release 4.99.3
https://www.openwall.com/lists/oss-security/2026/05/12/4Dead.Letter (CVE-2026-45185) – How XBOW found an unauthenticated RCE on Exim | Hacker News
https://news.ycombinator.com/item?id=48111748Index of /static/doc/security/EXIM-Security-2026-05-01.1/
https://exim.org/static/doc/security/EXIM-Security-2026-05-01.1/Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | eximon4 (4.86.2-2ubuntu2.6+esm9) @ xenial | 2026-06-28 | 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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
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 7× in last 7d / 48× 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 250 total refreshes for this CVE.
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 12:56 UTCVendor advisory
- 2026-06-28 12:56 UTCGHSA enrichment
- 2026-06-28 08:30 UTCGHSA enrichment
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-06-28 04:50 UTCVendor advisory
- 2026-06-28 04:50 UTCGHSA enrichment
- 2026-06-28 00:56 UTCVendor advisory
- 2026-06-28 00:56 UTCGHSA enrichment
- 2026-06-27 13:14 UTCVendor advisory
- 2026-06-27 13:14 UTCGHSA enrichment
- 2026-06-27 08:17 UTCVendor advisory
- 2026-06-27 08:17 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 20:41 UTCVendor advisory
- 2026-06-26 20:41 UTCGHSA enrichment
- 2026-06-26 04:00 UTCVendor advisory
- 2026-06-26 04:00 UTCGHSA enrichment
- 2026-06-25 20:33 UTCVendor advisory
- 2026-06-25 20:33 UTCGHSA enrichment
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 21:46 UTCVendor advisory
- 2026-06-17 21:46 UTCGHSA enrichment
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 15:00 UTCVendor advisory
- 2026-06-17 15:00 UTCGHSA enrichment
- 2026-06-17 03:21 UTCVendor advisory
- 2026-06-17 03:21 UTCGHSA enrichment
- 2026-06-16 23:11 UTCGHSA enrichment
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-16 11:32 UTCVendor advisory
- 2026-06-16 11:32 UTCGHSA enrichment
- 2026-06-16 07:34 UTCVendor advisory
- 2026-06-16 07:34 UTCGHSA enrichment
- 2026-06-16 03:56 UTCGHSA enrichment
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 05:26 UTCVendor advisory
- 2026-06-15 05:26 UTCGHSA enrichment
- 2026-06-15 01:46 UTCVendor advisory
- 2026-06-15 01:46 UTCGHSA enrichment
- 2026-06-14 22:08 UTCVendor advisory
- 2026-06-14 22:08 UTCGHSA enrichment
- 2026-06-14 18:28 UTCVendor advisory
- 2026-06-14 18:28 UTCGHSA enrichment
- 2026-06-14 14:22 UTCVendor advisory
- 2026-06-14 14:22 UTCGHSA enrichment
- 2026-06-14 10:03 UTCVendor advisory
- 2026-06-14 10:03 UTCGHSA enrichment
- 2026-06-14 06:24 UTCVendor advisory
- 2026-06-14 06:24 UTCGHSA enrichment
- 2026-06-14 00:02 UTCVendor advisory
- 2026-06-14 00:02 UTCGHSA enrichment
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 08:43 UTCGHSA enrichment
- 2026-06-13 04:59 UTCVendor advisory
- 2026-06-13 04:59 UTCGHSA enrichment
- 2026-06-13 00:05 UTCVendor advisory
- 2026-06-13 00:05 UTCGHSA enrichment
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 20:26 UTCVendor advisory
- 2026-06-12 20:26 UTCGHSA enrichment
- 2026-06-12 16:49 UTCVendor advisory
- 2026-06-12 16:49 UTCGHSA enrichment
- 2026-06-12 12:00 UTCVendor advisory
- 2026-06-12 12:00 UTCGHSA enrichment
- 2026-06-12 08:22 UTCVendor advisory
- 2026-06-12 08:22 UTCGHSA enrichment
- 2026-06-12 04:45 UTCVendor advisory
- 2026-06-12 04:45 UTCGHSA enrichment
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCliamromanis101/Dead.Letter-CVE-2026-45185First seen May 12, 2026
Dead.Letter CVE-2026-45185 EXIM Vulnerability Detection Script
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
Same CWE
10 shownCWE-416
- CVE-2010-3962NVD 8.1EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-0806NVD 8.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-0249NVD 8.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-4324NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-3328EG 8.8EPSS 98%HIGH
- CVE-2010-1772EG 8.8HIGH
- CVE-2010-1208EG 8.8EPSS 91%HIGH
- CVE-2010-0050EG 8.8EPSS 96%HIGH
- CVE-2010-0378EG 8.8EPSS 93%HIGH
- CVE-2009-3658EG 8.8EPSS 95%HIGH
Frequently asked(5)
What is CVE-2026-45185?
When was CVE-2026-45185 disclosed?
Is CVE-2026-45185 actively exploited?
What is the CVSS score of CVE-2026-45185?
How do I remediate CVE-2026-45185?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-45185
Is Your Infrastructure Affected by CVE-2026-45185?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.