End of life

MongoDB 5.0 end of life

MongoDB 5.0 end of life was 31 October 2024. MongoDB has shipped some 5.0 releases since, most recently 5.0.34 in 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.

What now

Which vendors provide MongoDB 5.0 security patches now that support has ended?

MongoDB 4.4 to 6.0 After End of Life: Patched Builds

Only your email is required · An engineer replies within 1 business day · No commitment

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. Dates checked on endoflife.date on 20 October 2026.

Last reviewed

MongoDB versions: release and end-of-life dates

MongoDB release and end-of-life dates
VersionReleasedEnd of lifeStatus
MongoDB 8.02 Oct 202431 October 2029Supported
MongoDB 7.01 Aug 202331 August 2027Approaching
MongoDB 6.05 Jul 202231 July 2025End of life
MongoDB 5.0 (this page)8 Jul 202131 October 2024End of life
MongoDB 4.425 Jul 202029 February 2024End of life

End-of-life dates are published by each project and checked against endoflife.date.

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.

CVEs published since MongoDB 5.0 ended

These are the CVEs in OSSeva's CVE directory that name MongoDB 5.0 and were published after 31 October 2024. MongoDB has shipped a fix on 5.0 for each so far, up to 5.0.34; its support policy does not promise the next.

Counts from the directory as of 20 October 2026 (MongoDB 5.0: 5 since 31 Oct 2024, 5 scored 7.0 or higher).

MongoDB CVEs published after each line ended, from the OSSeva CVE directory

LineCVECVSSPublishedIssueFixed upstream in
MongoDB 5.0CVE-2026-119338.812 Jun 2026MongoDB Server: use after free in server-side JavaScript BSON-to-array conversion5.0.34
MongoDB 5.0CVE-2026-80538.813 May 2026MongoDB Server: out-of-bounds write in time-series collections with duplicate field names5.0.33
MongoDB 5.0CVE-2025-148477.519 Dec 2025MongoDB Server: unauthenticated heap memory read through zlib-compressed message headers (MongoBleed)5.0.32
MongoDB 5.0CVE-2025-30859.81 Apr 2025MongoDB Server: intermediate certificates not checked for revocation on Linux5.0.31
MongoDB 5.0CVE-2024-109218.114 Nov 2024MongoDB Server: malformed BSON leads to buffer over-reads or crashes5.0.30

The directory lists MongoDB CVEs with a CVSS score of 7.0 or higher, matched at NVD to the product, so it is a subset of every MongoDB advisory. A CVE is listed when its affected range names the line and it was published after the line's end date. Fixed-in versions are from MongoDB's advisories. MongoDB's support policy does not oblige it to release fixes for ended lines.

Your options, costed honestly

Including the ones that do not involve buying anything from us.

OptionWhat it isEffortCostOur view
Upgrade to 8.0 or 9.0Sequential rolling upgrades with FCV steps.Scales with replica sets, shards, drivers and test coverageEngineering timeThe destination. 8.0 and 9.0 have the longer runways.
MongoDB ELS Add-OnUp to two years of support for one minor version after EOL.ProcurementAdd-on to Enterprise AdvancedFor Enterprise Advanced customers.
OSSeva patched builds on 5.0Committed fixes for self-managed Community Server 5.0.Starts from your current versionSubscription, priced per clusterFor Community Server estates that need a fix supply they can plan around.
Rely on discretionary releasesTake post-EOL releases when MongoDB ships them.NoneZero nowNot 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 support

What your auditor will say

PCI DSS v4 Requirement 6.3.3

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.

DORA

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.

Compliance library MongoDB end of life dates for every version

Questions

MongoDB 5.0: common questions

Book a 15-minute call

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 in 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.

Get a quote

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.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call