cve.bz

CVE-2026-45185 (Dead.Letter) exim exim: Use After Free

9.8 criticalEPSS 1.3%

Known as Dead.Letter

Critical (9.8) in exim exim. EPSS 1.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
1.3% (unchanged from 1.3% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 71st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-05-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-45185 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-45185?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-45185?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-45185 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Eximfrom 4.97 before 4.99.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11exim44.94.2-7+deb11u5DLA-4580-1
Debian12exim44.96-15+deb12u9DEBIAN-CVE-2026-45185 DSA-6265-1
Debian13exim44.98.2-1+deb13u2DEBIAN-CVE-2026-45185 DSA-6265-1
Debian14exim44.99.2-2DEBIAN-CVE-2026-45185
Ubuntu22.04:LTSexim44.95-4ubuntu2.8UBUNTU-CVE-2026-45185
Ubuntu24.04:LTSexim44.97-4ubuntu4.5UBUNTU-CVE-2026-45185
Ubuntu25.10exim44.98.2-1ubuntu2.2UBUNTU-CVE-2026-45185
Ubuntu26.04:LTSexim44.99.1-1ubuntu1.2UBUNTU-CVE-2026-45185
UbuntuPro:14.04:LTS, Pro:16.04:LTS, Pro:18.04:LTSexim4no fix listedUBUNTU-CVE-2026-45185 USN-8382-1
UbuntuPro:20.04:LTSexim44.93-13ubuntu1.12+esm1UBUNTU-CVE-2026-45185 USN-8382-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

References

Check your stackJSON