MuleSoft Runtime 4.13 · Version Status
MuleSoft Runtime 4.13 End of Life Date
MuleSoft Runtime 4.13 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.
✓
MuleSoft Runtime 4.13 is actively supported. EOL date: June 6, 2027.
📅 Get reminded before MuleSoft Runtime 4.13 reaches EOL on June 6, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Jun 6, 2027
221 days remaining
Latest Release
—
Standard release
Release Date
Oct 6, 2026
MuleSoft Runtime 4.13 series
Where these dates come from
End of lifeJun 6, 2027Vendor's own page (our correction) · mulesoft.com · checked Oct 28, 2026medium · 1 source agrees End of active supportMar 6, 2027Vendor's own page (our correction) · mulesoft.com · checked Oct 28, 2026medium · 1 source agrees ReleaseOct 6, 2026Vendor's own page (our correction) · mulesoft.com · checked Oct 28, 2026medium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
MuleSoft Runtime 4.13 was released on October 6, 2026 and support is scheduled to end on June 6, 2027 — a planned supported lifespan of 8 months, shorter than the 1 year median for MuleSoft Runtime releases. It is not an LTS release; MuleSoft Runtime reserves longer patch windows for its LTS versions.
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 →
All MuleSoft Runtime Versions
| Version | Latest | EOL Date | Status |
|---|
| 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 4, 2024 |
EOL |
| 4.6 Edge |
4.6.22 |
Oct 6, 2024 |
EOL |
What does MuleSoft Runtime 4.13 end of life mean?
When MuleSoft Runtime 4.13 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 MuleSoft Runtime 4.13 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to MuleSoft Runtime 4.13 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does MuleSoft Runtime 4.13 reach end of life?
MuleSoft Runtime 4.13 reaches end of life on June 6, 2027. That is 221 days remaining.
Is MuleSoft Runtime 4.13 still supported?
Yes, MuleSoft Runtime 4.13 is currently supported. The EOL date is June 6, 2027.
What should I upgrade to from MuleSoft Runtime 4.13?
The recommended upgrade from MuleSoft Runtime 4.13 is
MuleSoft Runtime 4.13 — 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.13 past EOL?
When MuleSoft Runtime 4.13 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 MuleSoft Runtime should migrate immediately or implement compensating controls.