MongoDB 8.0 end of life
MongoDB 8.0 reaches end of life on 31 October 2029, according to MongoDB's software lifecycle schedules. 8.0.0 was released on 2 October 2024, and the line still receives patch releases, most recently 8.0.34 on 24 September 2026. MongoDB 9.0, released in September 2026, is supported until 31 October 2031, and an 8.0 deployment upgrades to it in one step.
- End of life
- 31 October 2029
- Released
- Oct 2024
- Final release
- 8.0.34 (latest, 24 September 2026)
- Successor
- MongoDB 9.0 (to 31 October 2031)
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 2029
- Nothing yet. 8.0 receives patch releases with security fixes: 8.0.30 and 8.0.32, both from September 2026, each list CVE fixes.
- Patch releases and technical support for 8.0 after 31 October 2029.
- Driver compatibility, later. MongoDB states that drivers released more than three years after a server version's end-of-life date will not be compatible with it.
What actually breaks in the upgrade
One step to 9.0
MongoDB's 9.0 upgrade guide accepts deployments running 8.0 or 8.3. Upgrade each replica set and shard, then set featureCompatibilityVersion. Check that drivers support 9.0 before the servers move.
Estates on 7.0 go through 8.0
Earlier lines must upgrade one major version at a time until they reach 8.0. A 7.0 cluster, which reaches end of life on 31 August 2027, lands on 8.0 first in any case.
Keep 8.0 current meanwhile
8.0.30 and 8.0.32 both carry security fixes. A cluster several patch releases behind is exposed to issues MongoDB has already fixed, whatever the longer plan.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Stay on 8.0 and take each patch | MongoDB ships 8.0 patch releases until 31 October 2029. | Hours per release | Engineering time | The right answer for most estates today. |
| Upgrade to 9.0 | One rolling upgrade and a featureCompatibilityVersion change. | Weeks | Engineering time | Two more years of runway, to October 2031. |
| OSSeva support on 8.0 | Reviews, upgrade planning and operations for self-managed 8.0. | Days | Subscription | Puts 8.0 under the same contract as older MongoDB lines and the rest of the stack. |
What OSSeva does for MongoDB 8.0
OSSeva supports this line
MongoDB 8.0 is in OSSeva's MongoDB versions table as supported upstream, so fixes come from MongoDB's own 8.0 releases. Assure adds the authentication, TLS and network exposure review, a featureCompatibilityVersion upgrade plan and a driver compatibility audit; Operate adds 24/7 replica set and cluster monitoring and runs major version upgrades. OSSeva's patched builds cover 4.2 to 6.0 today.
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.
Auditors ask for evidence that production systems receive security fixes. A version past end of life fails that test unless another supplier ships the fixes and can show which CVEs they close.
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 8.0: common questions
What is the MongoDB 8.0 end of life date?
31 October 2029, according to MongoDB's software lifecycle schedules.
Is MongoDB 8.0 still supported?
Yes, until 31 October 2029. MongoDB released 8.0.34 on 24 September 2026.
What should I upgrade MongoDB 8.0 to?
MongoDB 9.0, released in September 2026 and supported until 31 October 2031. The upgrade from 8.0 is a single step.
Can MongoDB 7.0 upgrade directly to 9.0?
No. A 7.0 deployment upgrades to 8.0 first, then to 9.0.
Does MongoDB 8.0 need AVX?
Yes, on x86_64. MongoDB 5.0 and later require the AVX instruction set.
Still running MongoDB 8.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.