Approaching285 days from today

MongoDB 7.0 end of life

MongoDB 7.0 reaches end of life on 31 August 2027, according to MongoDB's software lifecycle schedules. It was released in August 2023 and still gets patch releases, most recently 7.0.48 in October 2026. MongoDB 8.0 is supported until 31 October 2029, and 9.0, released in September 2026, until 31 October 2031. Moving from 7.0 to 8.0 is one upgrade.

What now

Which vendors provide MongoDB 7.0 security patches after 31 August 2027?

MongoDB 4.4 to 6.0 After End of Life: Patched Builds
End of life
31 August 2027
Released
Aug 2023
Final release
7.0.48 (latest, October 2026)
Successor
MongoDB 8.0, or 9.0

Date published by MongoDB software lifecycle schedules. We do not publish a lifecycle date we cannot source.

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.0 (this page)1 Aug 202331 August 2027Approaching
MongoDB 6.05 Jul 202231 July 2025End of life
MongoDB 5.08 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 August 2027

  • Guaranteed patch releases for 7.0 after 31 August 2027. Any later release is at MongoDB's discretion.
  • Technical support for 7.0 under standard MongoDB subscriptions.
  • Fixes you can plan around. Until the end date, 7.0 gets the same CVE fixes as newer lines: CVE-2025-14847 was fixed in 7.0.28.

What actually breaks in the upgrade

One step to 8.0

MongoDB upgrades one major version at a time, so 7.0 to 8.0 is a single rolling upgrade of each replica set and shard, followed by setting featureCompatibilityVersion to 8.0. Check driver versions before the servers move.

Be on 7.0.28 or later now

CVE-2025-14847 lets an unauthenticated client read uninitialised heap memory through zlib-compressed protocol headers. It affects 7.0 before 7.0.28, and CISA added it to the Known Exploited Vulnerabilities catalogue on 29 December 2025. Whatever the longer plan, a 7.0 cluster below 7.0.28 should take the current 7.0 release first.

AVX is already a requirement

MongoDB 5.0 and later need the AVX instruction set on x86_64. A 7.0 estate already runs on hardware that meets it, so the CPU does not block the move to 8.0.

Your options, costed honestly

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

OptionWhat it isEffortCostOur view
Upgrade to 8.0One rolling upgrade and a featureCompatibilityVersion change.WeeksEngineering timeThe natural destination, supported to October 2029.
Stay on 7.0 until August 2027MongoDB keeps shipping 7.0 patch releases until the end date.NoneZero nowFine for now, as long as each 7.0 patch release is applied.
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 7.0Committed fixes for self-managed 7.0 Community Server after August 2027.DaysSubscriptionFor Community Server estates that need a fix supply they can plan around past the end date.

What OSSeva does for MongoDB 7.0

OSSeva patches this line

MongoDB 7.0 is in OSSeva's MongoDB coverage on the Patch, Assure and Operate tiers. Until 31 August 2027 the fixes come from MongoDB's own 7.0 releases; after that date OSSeva ships patched, signed builds of self-managed 7.0 Community Server. OSSeva engineers also run the featureCompatibilityVersion step to 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 7.0: common questions

Book a 15-minute call

When does MongoDB 7.0 reach end of life?

On 31 August 2027, according to MongoDB's software lifecycle schedules.

Is MongoDB 7.0 still supported?

Yes, until 31 August 2027. MongoDB released 7.0.45 in October 2026.

Is MongoDB 7.0 affected by CVE-2025-14847?

Versions before 7.0.28 are. The fix is in 7.0.28, released in December 2025, and CISA lists the flaw as known exploited.

How do I upgrade from MongoDB 7.0 to 8.0?

With one rolling upgrade of each replica set and shard, then setting featureCompatibilityVersion to 8.0.

What is the newest MongoDB version?

MongoDB 9.0, released in September 2026 and supported until 31 October 2031. MongoDB 8.0 is supported until 31 October 2029.

Get a quote

Still running MongoDB 7.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