The short answer
Mule 4.6 LTS left standard support in August 2026 and leaves extended support in February 2027. It is the last LTS that runs on Java 8 and 11; Mule 4.9 LTS (standard support to August 2027) and later run only on Java 17. Mule 4.10 removes TLS 1.0 and 1.1, so apps are auto-upgraded no further than the latest 4.9 patch and must be moved to 4.10 or later by hand.
Need someone who has run this upgrade?
Conntal places middleware engineers on contract, contract-to-hire or direct hire, each screened by a practitioner before you see a CV.
MuleSoft runs two release channels: Edge, with new features up to three times a year and short maintenance, and LTS, released periodically each February with at least 18 months of standard support and six months of extended support [1]. The LTS that most estates standardised on is now past its standard window.
| Version | Released | Java | End of standard support | End of extended support |
|---|---|---|---|---|
| 4.6 LTS | February 2024 | 8, 11, 17 | August 2026 | February 2027 |
| 4.9 LTS | February 2025 | 17 | August 2027 | February 2028 |
| 4.10 Edge | October 2025 | 17 | March 2026 | June 2026 |
Why 4.6 lasted longer than usual
MuleSoft gave 4.6 LTS an extended support window because of its compatibility with Java 8, 11 and 17 [1]. It is the bridge release: everything from 4.9 onward supports Java 17 only [1]. Moving off 4.6 is therefore a Java upgrade as much as a Mule upgrade — custom Java components, connectors and any library that assumed Java 8 behaviour come along for the ride.
The 4.10 line is a manual step
- Mule 4.10 removes support for TLS 1.0 and 1.1, which MuleSoft warns can break existing applications [1].
- For that reason, apps on Mule 4.9 or earlier are not auto-upgraded to 4.10 or later; apps on earlier versions such as 4.6 can be auto-upgraded only as far as the latest 4.9 patch [1].
- Reaching 4.10 or later requires upgrading the application manually [1].
What we ask
We ask MuleSoft developers what they would check before moving an estate from 4.6 to the 4.9 line, and what changes again at 4.10. Engineers who have done it talk about Java 17 compatibility of custom code and TLS on outbound connections; the rest talk about changing the runtime version in the deployment.
Need someone who has run this upgrade?
Conntal places middleware engineers on contract, contract-to-hire or direct hire, each screened by a practitioner before you see a CV.
Sources
- [1] MuleSoft (Salesforce), Edge and LTS Releases for Mule. Retrieved 31 October 2026.Primary source
Go deeper with the engineers who run it
Conntal is the staffing arm of AceMQ. When you need the platform supported rather than a person placed, these are the pages to read.
Related questions
When does Mule 4.6 LTS support end?
End of standard support was August 2026; end of extended support is February 2027.
Which Java version does Mule 4.9 support?
Java 17 only. Mule 4.6 LTS was the last LTS to support Java 8, 11 and 17.
Will MuleSoft auto-upgrade my app to Mule 4.10?
No. Because Mule 4.10 removes TLS 1.0 and 1.1, apps are auto-upgraded only as far as the latest Mule 4.9 patch; moving to 4.10 or later is a manual upgrade.