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 | 1635 days past EOL | EOL |
| 3.9 LTS | 3.9.5-20240122 | Oct 9, 2017 | Mar 20, 2024 | 780 days past EOL | EOL |
| 4.1 | 4.1.6-20240112 | Mar 20, 2018 | Nov 2, 2022 | 1284 days past EOL | EOL |
| 4.2 | 4.2.2-20221027 | May 2, 2019 | May 2, 2023 | 1103 days past EOL | EOL |
| 4.3 | 4.3.0-20240424 | Apr 30, 2020 | Mar 7, 2025 | 428 days past EOL | EOL |
| 4.4 | 4.4.0-20250919 | Sep 7, 2021 | Oct 8, 2025 | 213 days past EOL | EOL |
| 4.5 | 4.5.3 | Oct 31, 2023 | Jun 30, 2024 | 678 days past EOL | EOL |
| 4.6 | 4.6.22 | Feb 29, 2024 | Oct 31, 2024 | 555 days past EOL | EOL |
| 4.6-lts | 4.6.22 | Feb 29, 2024 | Feb 28, 2027 | 295 days remaining | Active |
| 4.7 | 4.7.4 | Jun 30, 2024 | Feb 28, 2025 | 435 days past EOL | EOL |
| 4.8 | 4.8.6 | Oct 31, 2024 | Jun 30, 2025 | 313 days past EOL | EOL |
| 4.9 | 4.9.16 | Feb 28, 2025 | Feb 28, 2026 | 70 days past EOL | EOL |
| 4.9-lts LTS | 4.9.16 | Feb 28, 2025 | Feb 29, 2028 | 661 days remaining | Active |
| 4.10 | 4.10.5 | Oct 31, 2025 | Jun 30, 2026 | 52 days remaining | Warning |
| 4.11 | 4.11.2 | Feb 28, 2026 | Oct 31, 2026 | 175 days remaining | Warning |
When a Mulesoft Runtime version 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →