MuleSoft Runtime 4.5 Edge · Version Status

MuleSoft Runtime 4.5 Edge End of Life Date

MuleSoft Runtime 4.5 Edge end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

MuleSoft Runtime 4.5 Edge is past end of life. This version no longer receives security patches. 775 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 30, 2024
775 days past EOL
Latest Release
4.5.3
Standard release
Release Date
Oct 31, 2023
MuleSoft Runtime 4.5 Edge series
Lifecycle detail

MuleSoft Runtime 4.5 was released on October 31, 2023 and support ended on June 30, 2024 — a supported lifespan of 8 months, shorter than the 3 years median for MuleSoft Runtime releases. It was not an LTS release; MuleSoft Runtime reserves longer patch windows for its LTS versions. The last patch it will ever receive is 4.5.3, published February 22, 2024 — 4 months before support ended. It has been without security patches for 2 years and 2 months. 6 newer MuleSoft Runtime releases have shipped since.

← MuleSoft Runtime 4.4 All MuleSoft Runtime versions MuleSoft Runtime 4.6 LTS →
50 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in 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 →
Recommended upgrade path
MuleSoft Runtime 4.12 Edge
Latest release: 4.12.1 · EOL: Feb 28, 2027
View full MuleSoft Runtime timeline →
Extended Support
Extended MuleSoft Runtime 4.5 Edge support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All MuleSoft Runtime Versions
VersionLatestEOL DateStatus
3.8 LTS 3.8.7 Nov 16, 2021 EOL
3.9 LTS 3.9.5-20240122 Mar 20, 2024 EOL
4.1 4.1.6-20240112 Nov 2, 2022 EOL
4.2 4.2.2-20221027 May 2, 2023 EOL
4.3 4.3.0-20240424 Mar 7, 2025 EOL
4.4 4.4.0-20250919 Oct 8, 2025 EOL
4.5 Edge 4.5.3 Jun 30, 2024 EOL
4.6 Edge 4.6.22 Oct 31, 2024 EOL

What does MuleSoft Runtime 4.5 Edge end of life mean?

When MuleSoft Runtime 4.5 Edge 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running MuleSoft Runtime 4.5 Edge past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to MuleSoft Runtime 4.12 Edge or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does MuleSoft Runtime 4.5 Edge reach end of life?
MuleSoft Runtime 4.5 Edge reached end of life on June 30, 2024. This version is no longer receiving security patches.
Is MuleSoft Runtime 4.5 Edge still supported?
No. MuleSoft Runtime 4.5 Edge reached end of life on June 30, 2024 and is no longer receiving security patches.
What should I upgrade to from MuleSoft Runtime 4.5 Edge?
The recommended upgrade from MuleSoft Runtime 4.5 Edge is MuleSoft Runtime 4.12 Edge — the latest actively supported version. Check the MuleSoft Runtime full timeline for all supported versions.
What are the security risks of running MuleSoft Runtime 4.5 Edge past EOL?
When MuleSoft Runtime 4.5 Edge reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL MuleSoft Runtime should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →