Exim End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Exim versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 4.50 | 4.50 | Feb 17, 2005 | May 4, 2005 | 7767 days past EOL | EOL |
| 4.51 | 4.51 | May 4, 2005 | Jul 1, 2005 | 7709 days past EOL | EOL |
| 4.52 | 4.52 | Jul 1, 2005 | Sep 26, 2005 | 7622 days past EOL | EOL |
| 4.53 | 4.53 | Sep 26, 2005 | Oct 4, 2005 | 7614 days past EOL | EOL |
| 4.54 | 4.54 | Oct 4, 2005 | Apr 5, 2006 | 7431 days past EOL | EOL |
| 4.61 | 4.61 | Apr 4, 2006 | Apr 29, 2006 | 7407 days past EOL | EOL |
| 4.62 | 4.62 | Apr 28, 2006 | Aug 1, 2006 | 7313 days past EOL | EOL |
| 4.63 | 4.63 | Jul 31, 2006 | Dec 20, 2006 | 7172 days past EOL | EOL |
| 4.64 | 4.64 | Dec 20, 2006 | Jan 2, 2007 | 7159 days past EOL | EOL |
| 4.65 | 4.65 | Jan 2, 2007 | Jan 8, 2007 | 7153 days past EOL | EOL |
| 4.66 | 4.66 | Jan 8, 2007 | Apr 18, 2007 | 7053 days past EOL | EOL |
| 4.67 | 4.67 | Apr 17, 2007 | Aug 31, 2007 | 6918 days past EOL | EOL |
| 4.68 | 4.68 | Aug 30, 2007 | Dec 2, 2007 | 6825 days past EOL | EOL |
| 4.69 | 4.69 | Dec 1, 2007 | Nov 14, 2009 | 6112 days past EOL | EOL |
| 4.70 | 4.70 | Nov 13, 2009 | Nov 24, 2009 | 6102 days past EOL | EOL |
| 4.71 | 4.71 | Nov 23, 2009 | Jun 3, 2010 | 5911 days past EOL | EOL |
| 4.72 | 4.72 | Jun 3, 2010 | Dec 27, 2010 | 5704 days past EOL | EOL |
| 4.73 | 4.73 | Dec 26, 2010 | Jan 25, 2011 | 5675 days past EOL | EOL |
| 4.74 | 4.74 | Jan 24, 2011 | Mar 22, 2011 | 5619 days past EOL | EOL |
| 4.75 | 4.75 | Mar 22, 2011 | May 9, 2011 | 5571 days past EOL | EOL |
| 4.76 | 4.76 | May 9, 2011 | Oct 10, 2011 | 5417 days past EOL | EOL |
| 4.77 | 4.77 | Oct 10, 2011 | May 31, 2012 | 5183 days past EOL | EOL |
| 4.80 | 4.80.1 | May 31, 2012 | Oct 28, 2013 | 4668 days past EOL | EOL |
| 4.82 | 4.82.1 | Oct 28, 2013 | Jul 21, 2014 | 4402 days past EOL | EOL |
| 4.83 | 4.83 | Jul 21, 2014 | Aug 11, 2014 | 4381 days past EOL | EOL |
| 4.84 | 4.84.2 | Aug 11, 2014 | Jan 12, 2015 | 4227 days past EOL | EOL |
| 4.85 | 4.85.2 | Jan 12, 2015 | Jul 26, 2015 | 4032 days past EOL | EOL |
| 4.86 | 4.86.2 | Jul 26, 2015 | Apr 6, 2016 | 3777 days past EOL | EOL |
| 4.87 | 4.87.1 | Apr 6, 2016 | Dec 18, 2016 | 3521 days past EOL | EOL |
| 4.88 | 4.88 | Dec 18, 2016 | Mar 7, 2017 | 3442 days past EOL | EOL |
| 4.89 | 4.89.1 | Mar 7, 2017 | Dec 19, 2017 | 3155 days past EOL | EOL |
| 4.90 | 4.90.1 | Dec 19, 2017 | Apr 15, 2018 | 3038 days past EOL | EOL |
| 4.91 | 4.91 | Apr 15, 2018 | Feb 10, 2019 | 2737 days past EOL | EOL |
| 4.92 | 4.92.3 | Feb 10, 2019 | Dec 8, 2019 | 2436 days past EOL | EOL |
| 4.93 | 4.93.0.4 | Dec 8, 2019 | Jun 1, 2020 | 2260 days past EOL | EOL |
| 4.94 | 4.94.2 | Jun 1, 2020 | Sep 28, 2021 | 1776 days past EOL | EOL |
| 4.95 | 4.95 | Sep 28, 2021 | Jun 25, 2022 | 1506 days past EOL | EOL |
| 4.96 | 4.96.2 | Jun 25, 2022 | Nov 4, 2023 | 1009 days past EOL | EOL |
| 4.97 | 4.97.1 | Nov 4, 2023 | Jul 10, 2024 | 760 days past EOL | EOL |
| 4.98 | 4.98.2 | Jul 10, 2024 | Oct 28, 2025 | 285 days past EOL | EOL |
| 4.99 | 4.99.1 | Oct 28, 2025 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/exim)
What does Exim end of life mean for your organization?
When a version of Exim reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Exim should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Exim reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Exim versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Exim has 40 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Exim exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.