MongoDB 5.0 end of life
MongoDB 5.0 reached end of life on 31 October 2024. MongoDB has shipped some 5.0 releases since, most recently 5.0.34 on 10 June 2026, but its support policy carries no obligation to patch versions past end of life. 5.0 is also the first line that needs AVX on x86_64. OSSeva ships patched MongoDB 5.0 builds with a committed fix supply.
- End of life
- 31 October 2024
- Released
- Jul 2021
- Final release
- 5.0.34 (latest known, June 2026)
- Successor
- MongoDB 7.0 or 8.0, via 6.0
Date published by MongoDB software lifecycle schedules. We do not publish a lifecycle date we cannot source.
Last reviewed
What actually stops on 31 October 2024
- Guaranteed patch releases for 5.0. Any post-EOL release is at MongoDB's discretion.
- Technical support for 5.0 under standard MongoDB subscriptions.
- Fixes you can plan around. 5.0.32 carried the fix for CVE-2025-14847, which CISA added to its known exploited list on 29 December 2025, but nothing obliged MongoDB to ship it.
What actually breaks in the upgrade
Three upgrades to reach 8.0
MongoDB upgrades one major version at a time: 5.0 to 6.0, 6.0 to 7.0, 7.0 to 8.0, raising featureCompatibilityVersion after each step. Every step is a rolling upgrade of each replica set and shard.
AVX is already a requirement
MongoDB 5.0 and later need the AVX instruction set on x86_64. A 5.0 estate already runs on hardware that meets it, so the CPU does not block the move forward, but it does block any fallback to hosts without AVX.
Check the landing dates
MongoDB 7.0 is supported until 31 August 2027 and 8.0 until 31 October 2029. A move to 7.0 alone buys under a year.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to 8.0 | Three sequential rolling upgrades with FCV steps. | Weeks to months | Engineering time | The destination. 8.0 has the longer runway. |
| MongoDB ELS Add-On | Up to two years of support for one minor version after EOL. | Procurement | Add-on to Enterprise Advanced | For Enterprise Advanced customers. |
| OSSeva patched builds on 5.0 | Committed fixes for self-managed Community Server 5.0. | Days | Subscription | For Community Server estates that need a fix supply they can plan around. |
| Rely on discretionary releases | Take post-EOL releases when MongoDB ships them. | None | Zero now | Not evidence an auditor accepts, because nothing commits to the next one. |
What OSSeva does for MongoDB 5.0
OSSeva patches this line
OSSeva ships patched, signed builds of self-managed MongoDB 5.0 Community Server with committed CVE fixes, on the Patch, Assure and Operate tiers. OSSeva engineers also run the featureCompatibilityVersion steps to 6.0, 7.0 and 8.0.
MongoDB extended supportWhat your auditor will say
The data store is a system component in its own right. An unsupported version with no patch source is a finding; a documented third-party patch stream is the usual remediation.
For EU financial entities, the ICT risk and third-party provisions apply when a critical service depends on software with no support arrangement in place.
MongoDB 5.0: common questions
When did MongoDB 5.0 reach end of life?
On 31 October 2024.
Is MongoDB 5.0 still getting patches?
Occasionally. MongoDB released 5.0.34 on 10 June 2026, but its policy carries no obligation to patch versions past end of life.
Was MongoDB 5.0 patched for CVE-2025-14847?
Yes. The fix is in 5.0.32, released in December 2025. CISA added the flaw to its known exploited vulnerabilities catalogue on 29 December 2025.
How do I upgrade from MongoDB 5.0 to 8.0?
One major version at a time: 5.0 to 6.0, then 7.0, then 8.0, setting featureCompatibilityVersion after each step.
Still running MongoDB 5.0?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.