MuleSoft Runtime End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all MuleSoft Runtime versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.8 LTS | 3.8.7 | May 16, 2016 | Nov 16, 2021 | 1698 days past EOL | EOL |
| 3.9 LTS | 3.9.5-20240122 | Oct 9, 2017 | Mar 20, 2024 | 843 days past EOL | EOL |
| 4.1 | 4.1.6-20240112 | Mar 20, 2018 | Nov 2, 2022 | 1347 days past EOL | EOL |
| 4.2 | 4.2.2-20221027 | May 2, 2019 | May 2, 2023 | 1166 days past EOL | EOL |
| 4.3 | 4.3.0-20240424 | Apr 30, 2020 | Mar 7, 2025 | 491 days past EOL | EOL |
| 4.4 | 4.4.0-20250919 | Sep 7, 2021 | Oct 8, 2025 | 276 days past EOL | EOL |
| 4.5 | 4.5.3 | Oct 31, 2023 | Jun 30, 2024 | 741 days past EOL | EOL |
| 4.6 | 4.6.22 | Feb 29, 2024 | Oct 31, 2024 | 618 days past EOL | EOL |
| 4.6-lts | 4.6.22 | Feb 29, 2024 | Feb 28, 2027 | 232 days remaining | Active |
| 4.7 | 4.7.4 | Jun 30, 2024 | Feb 28, 2025 | 498 days past EOL | EOL |
| 4.8 | 4.8.6 | Oct 31, 2024 | Jun 30, 2025 | 376 days past EOL | EOL |
| 4.9 | 4.9.16 | Feb 28, 2025 | Feb 28, 2026 | 133 days past EOL | EOL |
| 4.9-lts LTS | 4.9.16 | Feb 28, 2025 | Feb 29, 2028 | 598 days remaining | Active |
| 4.10 | 4.10.5 | Oct 31, 2025 | Jun 30, 2026 | 11 days past EOL | EOL |
| 4.11 | 4.11.2 | Feb 28, 2026 | Oct 31, 2026 | 112 days remaining | Warning |
What does MuleSoft Runtime end of life mean for your organization?
When a version of MuleSoft Runtime 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 MuleSoft Runtime 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL MuleSoft Runtime versions. This is a bridge, not a permanent solution — plan your migration in parallel.
MuleSoft Runtime has 12 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.
Get My Support Options →