MongoDB Versions: Release, EOL and Latest Patch for Every Version

MongoDB 9.0 is the newest version, at patch 9.0.4. The next end of life is 7.0 on 31 August 2027, then 8.0 and 8.3 on 31 October 2029 and 9.0 on 31 October 2031. Ended already: 6.0 (31 July 2025), 5.0 (31 October 2024), 4.4 (29 February 2024), 4.2 (30 April 2023). Dates checked against MongoDB's lifecycle schedules and endoflife.date on 22 October 2026.

MongoDB supports each major server release, such as 8.0 or 9.0, for five years from its release date. Minor releases from 8.2 onward each get an end date in MongoDB's published lifecycle schedule, and those windows vary widely, so check the table above rather than assuming a fixed term.

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

Latest release
9.0.8
Supported lines
4
End-of-life lines
29
Next end of life
7.0 · 31 Aug 2027

Held on 4.4 by the hardware?

MongoDB 4.4 on hardware without AVX

MongoDB 5.0 and later need the AVX instruction set on x86_64, so 4.4 is the newest line a host without it can run. The solution page maps each CPU family to the newest line it starts, lists the CVEs published since 4.4, 5.0 and 6.0 ended, and shows how patched builds cover the hosts that cannot move yet.

Who patches MongoDB after end of life

OSSeva provides MongoDB extended support: patched, signed builds for MongoDB 6.0, 5.0, 4.4 and 4.2 after upstream support ends, plus 24/7 operations on the Operate tier.

MongoDB release timeline

Security SupportTodayChart shows the 14 newest lines; the table lists all.

All MongoDB versions, release dates and end-of-life dates

VersionReleasedSecurity SupportLatestOSSeva
9.02 months ago(30 Sept 2026)Ends in 4 years and 11 months(31 Oct 2031)9.0.8–
8.36 months ago(31 May 2026)Ends in 2 years and 11 months(31 Oct 2029)8.3.17–
8.2 (Rapid Release)1 year and 2 months ago(30 Sept 2025)Ended 4 months ago(31 Jul 2026)8.2.12–
8.1 (Rapid Release)1 year and 5 months ago(30 Jun 2025)Ended 1 year and 2 months ago(30 Sept 2025)8.1.3–
8.0MongoDB 8.0 end of life2 years and 1 month ago(31 Oct 2024)Ends in 2 years and 11 months(31 Oct 2029)8.0.38–
7.3 (Rapid Release)2 years and 8 months ago(31 Mar 2024)Ended 2 years and 1 month ago(2 Oct 2024)7.3.4–
7.2 (Rapid Release)2 years and 10 months ago(31 Jan 2024)Ended 2 years and 8 months ago(27 Mar 2024)7.2.2–
7.1 (Rapid Release)3 years and 1 month ago(31 Oct 2023)Ended 2 years and 10 months ago(23 Jan 2024)7.1.1–
7.0MongoDB 7.0 end of life3 years and 3 months ago(31 Aug 2023)Ends in 9 months(31 Aug 2027)7.0.48–
6.3 (Rapid Release)3 years and 7 months ago(30 Apr 2023)Ended 3 years and 3 months ago(31 Aug 2023)6.3.2–
6.2 (Rapid Release)3 years and 9 months ago(28 Feb 2023)Ended 3 years and 7 months ago(24 Apr 2023)6.2.1–
6.1 (Rapid Release)4 years and 1 month ago(31 Oct 2022)Ended 3 years and 9 months ago(9 Feb 2023)6.1.1–
6.0MongoDB 6.0 end of life4 years and 4 months ago(31 Jul 2022)Ended 1 year and 4 months ago(31 Jul 2025)6.0.30 Patched
5.3 (Rapid Release)4 years and 8 months ago(31 Mar 2022)Ended 4 years and 4 months ago(19 Jul 2022)5.3.2–
5.2 (Rapid Release)4 years and 9 months ago(31 Jan 2022)Ended 4 years and 8 months ago(23 Mar 2022)5.2.1–
5.1 (Rapid Release)5 years ago(30 Nov 2021)Ended 4 years and 10 months ago(19 Jan 2022)5.1.1–
5.0MongoDB 5.0 end of life5 years and 4 months ago(31 Jul 2021)Ended 2 years and 1 month ago(31 Oct 2024)5.0.35 Patched
4.4MongoDB 4.4 end of life6 years and 4 months ago(31 Jul 2020)Ended 2 years and 9 months ago(29 Feb 2024)4.4.32 Patched
4.27 years and 3 months ago(31 Aug 2019)Ended 3 years and 7 months ago(30 Apr 2023)4.2.25 Patched
4.08 years and 5 months ago(30 Jun 2018)Ended 4 years and 7 months ago(30 Apr 2022)4.0.28–
3.69 years ago(30 Nov 2017)Ended 5 years and 7 months ago(30 Apr 2021)3.6.23–
3.410 years ago(30 Nov 2016)Ended 6 years and 10 months ago(31 Jan 2020)3.4.24–
3.210 years and 11 months ago(31 Dec 2015)Ended 8 years and 2 months ago(30 Sept 2018)3.2.22–
3.011 years and 8 months ago(31 Mar 2015)Ended 8 years and 9 months ago(28 Feb 2018)3.0.15–
2.612 years and 7 months ago(7 Apr 2014)Ended 10 years ago(31 Oct 2016)2.6.12–
2.413 years and 8 months ago(18 Mar 2013)Ended 13 years and 8 months ago(31 Mar 2013)2.4.14–
2.214 years and 3 months ago(28 Aug 2012)Ended 12 years and 9 months ago(28 Feb 2014)2.2.7–
2.015 years and 2 months ago(11 Sept 2011)Ended 13 years and 8 months ago(31 Mar 2013)2.0.9–
1.815 years and 8 months ago(16 Mar 2011)Ended 14 years and 2 months ago(30 Sept 2012)1.8.5–
1.616 years and 3 months ago(5 Aug 2010)Ended 14 years and 9 months ago(28 Feb 2012)1.6.5–
1.416 years and 8 months ago(25 Mar 2010)Ended 14 years and 2 months ago(30 Sept 2012)1.4.5–
1.216 years and 11 months ago(10 Dec 2009)Ended 15 years and 5 months ago(30 Jun 2011)1.2.5–
1.017 years and 3 months ago(27 Aug 2009)Ended 16 years and 3 months ago(31 Aug 2010)1.0.1–

Lifecycle data from endoflife.date (MIT licence), refreshed 15 Nov 2026. Upstream policy: www.mongodb.com. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.

MongoDB versions: end of life, latest patch and CVEs since

One row per version MongoDB still lists or recently ended. The last column counts the CVEs in OSSeva's CVE directory that name the version and were published after its end-of-life date. The directory holds CVEs scored 7.0 or higher, so the counts are a floor, not every advisory.

MongoDB versions, end-of-life dates, latest patch and CVEs since end of life

VersionReleasedEnd of lifeLatest patchCVEs since end of life
9.0September 202631 Oct 20319.0.4Supported
8.3May 202631 Oct 20298.3.13Supported
8.0October 202431 Oct 20298.0.34Supported
7.0August 202331 Aug 20277.0.45Supported
6.0July 202231 Jul 20256.0.293
5.0July 202131 Oct 20245.0.345
4.4July 202029 Feb 20244.4.313
4.2August 201930 Apr 20234.2.251

End-of-life and release months are from MongoDB's software lifecycle schedules (Enterprise Advanced table). Latest patches are from endoflife.date, with 8.0.34 confirmed on MongoDB's changelog, checked 22 October 2026. MongoDB has shipped a fix on the ended lines for every counted CVE so far, but its support policy does not promise the next.

What end of life means for MongoDB

MongoDB supports each major release for a fixed window set out in its software lifecycle schedules. After the end-of-life date it owes no more fixes for the line. It has published some anyway, the newest being 4.4.31, 5.0.34 and 6.0.29 in June 2026, but its support policy does not promise a next release, and 4.2 got no fix for CVE-2025-14847, which CISA lists as exploited.

MongoDB also states that drivers released more than three years after a server version's end-of-life date are not compatible with that version, so an ended line gets harder to keep connected to current applications as well as harder to keep patched.

CVEs published since each MongoDB line ended

These are the CVEs in OSSeva's CVE directory that name each line and were published after it reached end of life. MongoDB has shipped a fix on the ended lines for every one of them so far.

Counts from the directory as of 20 October 2026 (MongoDB 4.4: 3 since 29 Feb 2024, 3 scored 7.0 or higher; MongoDB 5.0: 5 since 31 Oct 2024, 5 scored 7.0 or higher; MongoDB 6.0: 3 since 31 Jul 2025, 3 scored 7.0 or higher).

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

LineCVECVSSPublishedIssueFixed upstream in
MongoDB 4.4CVE-2026-119338.812 Jun 2026MongoDB Server: use after free in server-side JavaScript BSON-to-array conversion4.4.31
MongoDB 4.4CVE-2025-148477.519 Dec 2025MongoDB Server: unauthenticated heap memory read through zlib-compressed message headers (MongoBleed)4.4.30
MongoDB 4.4CVE-2024-13519.87 Mar 2024MongoDB Server: peer certificate validation skipped when TLS is enabled without a CA file4.4.29
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
MongoDB 6.0CVE-2026-119338.812 Jun 2026MongoDB Server: use after free in server-side JavaScript BSON-to-array conversion6.0.29
MongoDB 6.0CVE-2026-80538.813 May 2026MongoDB Server: out-of-bounds write in time-series collections with duplicate field names6.0.28
MongoDB 6.0CVE-2025-148477.519 Dec 2025MongoDB Server: unauthenticated heap memory read through zlib-compressed message headers (MongoBleed)6.0.27

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.

Upgrade, move to Atlas, or run patched builds

Upgrading is the destination: 7.0, 8.0 or 9.0, one major version at a time, raising featureCompatibilityVersion at each step. Scope follows the number of replica sets and shards, the drivers in use and how well the application is tested. From 5.0 on, every host needs a CPU with AVX.

Atlas moves patching to MongoDB and brings a migration and a new cost model. The ELS Add-On extends support for Enterprise Advanced customers only. For self-managed Community Server that cannot move before an audit or scanner deadline, patched builds keep the line covered while the upgrade is planned; support is priced per cluster.

Running an end-of-life MongoDB version?

OSSeva keeps end-of-life MongoDB patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.

MongoDB extended support

Questions

MongoDB end of life: common questions

Book a 15-minute call

What is the latest MongoDB version?

MongoDB 9.0, released in September 2026, at patch 9.0.4. MongoDB 8.0 is at 8.0.34 and 7.0 at 7.0.45. Latest patches checked on 22 October 2026.

When is MongoDB 4.4 end of life?

MongoDB 4.4 reached end of life on 29 February 2024. 5.0 followed on 31 October 2024 and 6.0 on 31 July 2025. Dates checked on 22 October 2026.

Is MongoDB 7.0 end of life?

Not yet. MongoDB 7.0 ends on 31 August 2027. MongoDB 8.0 ends on 31 October 2029 and 9.0 on 31 October 2031.

Who provides MongoDB support after end of life?

MongoDB sells an Extended Lifecycle Support add-on to Enterprise Advanced customers. For self-managed Community Server, OSSeva ships patched, signed builds of 4.4, 5.0 and 6.0, including 4.4 on hardware without AVX.

Is MongoDB 6.0 end of life?

Yes. MongoDB 6.0 reached end of life on 31 July 2025, three years after its July 2022 release, under the lifecycle schedule that applied to it. MongoDB no longer supports 6.0 or ships fixes for it, so deployments still on 6.0 need an upgrade or third-party support to keep receiving security patches.

When is MongoDB 7.0 end of life?

MongoDB's lifecycle schedule lists 31 August 2027 as the end-of-life date for MongoDB 7.0, which was released in August 2023. MongoDB 8.0 runs to 31 October 2029 and MongoDB 9.0, released in September 2026, to 31 October 2031, so both give much more runway than staying on 7.0.

Is MongoDB 5.0 end of life?

Yes. MongoDB 5.0 reached end of life on 31 October 2024, a little over three years after its July 2021 release. MongoDB ships no fixes for 5.0, and MongoDB drivers released more than three years after a server version's end-of-life date will not be compatible with it.

When is the next MongoDB end of life?

MongoDB 7.0 reaches the end of security support on 31 Aug 2027. After that date the project stops shipping security fixes for 7.0, and CVEs disclosed later stay unpatched upstream.

Which MongoDB versions are still supported?

9.0 (until 31 Oct 2031), 8.3 (until 31 Oct 2029), 8.0 (until 31 Oct 2029) and 7.0 (until 31 Aug 2027). Every other line has reached end of life, per the dates in the table above.

Can I get security patches for an end-of-life MongoDB version?

Yes. OSSeva ships signed builds with backported CVE fixes for MongoDB 6.0, 5.0, 4.4 and 4.2 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.

Get a quote

Still running an end-of-life MongoDB?

Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.

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

Prefer to talk or read more first?

Book a call