Exim 4.100 · Version Status

Exim 4.100 End of Life Date

Exim 4.100 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

✓ Exim 4.100 is actively supported. No end-of-life date has been announced yet.
EOL Date
TBD
Supported
Latest Release
4.100.1
Standard release
Release Date
Aug 20, 2026
Exim 4.100 series
Lifecycle detail

Exim 4.100 was released on August 20, 2026 and has no published end-of-life date yet. Its most recent patch is 4.100.1, published September 14, 2026.

← Exim 4.99 All Exim versions
30 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All Exim Versions
VersionLatestEOL DateStatus
4.50 4.50 May 4, 2005 EOL
4.51 4.51 Jul 1, 2005 EOL
4.52 4.52 Sep 26, 2005 EOL
4.53 4.53 Oct 4, 2005 EOL
4.54 4.54 Apr 5, 2006 EOL
4.61 4.61 Apr 29, 2006 EOL
4.62 4.62 Aug 1, 2006 EOL
4.63 4.63 Dec 20, 2006 EOL

What does Exim 4.100 end of life mean?

When Exim 4.100 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Exim 4.100 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Exim 4.100 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Exim 4.100 reach end of life?
Exim 4.100 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is Exim 4.100 still supported?
Yes, Exim 4.100 is currently supported. The EOL date is TBD.
What should I upgrade to from Exim 4.100?
The recommended upgrade from Exim 4.100 is Exim 4.100 — the latest actively supported version. Check the Exim full timeline for all supported versions.
What are the security risks of running Exim 4.100 past EOL?
When Exim 4.100 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Exim should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →