Is MongoDB Still Supported? End-of-Life Dates (2026)
Short answer
MongoDB is supported and new versions continue to ship; the newest version is supported until 31 Oct 2031. CISA’s Known Exploited Vulnerabilities catalog lists 1 vulnerability in MongoDB.
MongoDB is a supported product, so the exposure is in the version you run: MongoDB 6.0 and earlier have passed end of life, and Community Edition has been under the SSPL rather than the AGPL since 16 October 2018.
Legacy Technology Tracker · Status as of 16 Oct 2026. Data checked 7 Oct 2026; refreshed monthly, with quarterly snapshots kept unchanged.
Risk rating
Low: supported, with new release lines continuing; no licence change recorded in the last 24 months; 1 vulnerability on CISA's KEV list (supported versions receive security fixes). How ratings work
Key facts
Every value links to its source and shows when we last checked or retrieved it. Data checked 7 Oct 2026; status as of 16 Oct 2026.
| Fact | Value | Source | Checked |
|---|---|---|---|
| Support status | SupportedMongoDB Server releases. | ||
| Newest version supported until | |||
| Known exploited vulnerabilities (CISA KEV) | 1 CVE all time; 1 added in the last 24 monthsNewest added 29 Dec 2025Matched by vendor and product name in the KEV catalog. | ||
| Last release | r7.0.43, 11 Sep 2026Maintainer: MongoDB, Inc. | ||
| Licence change | : MongoDB Community Server releases moved from AGPL to the Server Side Public License (SSPL) | ||
| Job postings and salaries | Not published: the job-posting source is on hold pending a data licence. | — | — |
Versions in scope
MongoDB Server releases. Dates per version, each with its source.
| Version | Status | Standard support ends | Extended support ends | Latest release | Source | Checked |
|---|---|---|---|---|---|---|
| 1.0 | Unsupported | — | 1.0.1 (22 Oct 2009) | |||
| 1.2 | Unsupported | — | 1.2.5 (7 Apr 2010) | |||
| 1.4 | Unsupported | — | 1.4.5 (31 Aug 2010) | |||
| 1.6 | Unsupported | — | 1.6.5 (8 Dec 2010) | |||
| 1.8 | Unsupported | — | 1.8.5 (1 Feb 2012) | |||
| 2.0 | Unsupported | — | 2.0.9 (2 Apr 2013) | |||
| 2.2 | Unsupported | — | 2.2.7 (15 Jan 2014) | |||
| 2.4 | Unsupported | — | 2.4.14 (27 Apr 2015) | |||
| 2.6 | Unsupported | — | 2.6.12 (22 Mar 2016) | |||
| 3.0 | Unsupported | — | 3.0.15 (10 May 2017) | |||
| 3.2 | Unsupported | — | 3.2.22 (26 Dec 2018) | |||
| 3.4 | Unsupported | — | 3.4.24 (24 Jan 2020) | |||
| 3.6 | Unsupported | — | 3.6.23 (16 Mar 2021) | |||
| 4.0 | Unsupported | — | 4.0.28 (24 Jan 2022) | |||
| 4.2 | Unsupported | — | 4.2.25 (4 Dec 2023) | |||
| 4.4 | Unsupported | — | 4.4.31 (24 Jun 2026) | |||
| 5.0 | Unsupported | — | 5.0.34 (16 Jun 2026) | |||
| 5.1 | Unsupported | — | 5.1.1 (1 Dec 2021) | |||
| 5.2 | Unsupported | — | 5.2.1 (17 Feb 2022) | |||
| 5.3 | Unsupported | — | 5.3.2 (15 Jun 2022) | |||
| 6.0 | Unsupported | — | 6.0.29 (16 Jun 2026) | |||
| 6.1 | Unsupported | — | 6.1.1 (3 Jan 2023) | |||
| 6.2 | Unsupported | — | 6.2.1 (28 Feb 2023) | |||
| 6.3 | Unsupported | — | 6.3.2 (28 Jun 2023) | |||
| 7.0 | Supported | — | 7.0.43 (11 Sep 2026) | |||
| 7.1 | Unsupported | — | 7.1.1 (16 Nov 2023) | |||
| 7.2 | Unsupported | — | 7.2.2 (28 Feb 2024) | |||
| 7.3 | Unsupported | — | 7.3.4 (14 Aug 2024) | |||
| 8.0 | Supported | — | 8.0.32 (11 Sep 2026) | |||
| 8.1 | Unsupported | — | 8.1.3 (8 Aug 2025) | |||
| 8.2 | Unsupported | — | 8.2.12 (28 Jul 2026) | |||
| 8.3 | Supported | — | 8.3.11 (11 Sep 2026) | |||
| 9.0 | Supported | — | 9.0.2 (28 Sep 2026) |
If you still run MongoDB
The date that matters is your release line's end of life. MongoDB 6.0 and earlier are past it, 7.0 ends on 31 August 2027, and 8.0 and 8.3 on 31 October 2029, according to MongoDB's lifecycle schedule for Enterprise Advanced.
The realistic options:
- Upgrade MongoDB. Move to a supported release. Upgrades go one major version at a time, so a deployment on 5.0 or earlier needs several steps, each with testing. Check driver compatibility too: MongoDB states that drivers released more than three years after a server version's end of life will not be compatible with that server version.
- Use MongoDB Atlas. The managed service has its own lifecycle schedule on the same MongoDB page, so ask MongoDB how version upgrades work for your cluster tier.
- Migrate to another database. Some teams whose data fits a relational model move to PostgreSQL. MongoDB to PostgreSQL migration covers schema normalization, query rewrite, downtime planning and cost ranges.
If licensing is the concern rather than the version, read the SSPL terms for how you use MongoDB before deciding.
For suppliers, see data modernization companies. Modernization costs gives budget context.
Frequently asked questions
Is MongoDB still supported?
Yes. MongoDB publishes an end-of-life date for every release in its lifecycle schedules. For self-managed Enterprise Advanced, 7.0 is supported until 31 August 2027, 8.0 and 8.3 until 31 October 2029, and 9.0 until 31 October 2031.
Which MongoDB versions are end of life?
Per the same schedule, MongoDB 6.0 reached end of life on 31 July 2025, 5.0 on 31 October 2024, 4.4 on 29 February 2024 and 4.2 on 30 April 2023. Every earlier release is also past its date.
Is MongoDB open source after the licence change?
On 16 October 2018 MongoDB moved Community Server from the AGPL to the Server Side Public License (SSPL), which adds conditions for anyone offering MongoDB as a publicly available service (MongoDB's SSPL FAQ). If you only run it for your own applications, check the terms with counsel.
How do I upgrade MongoDB past an end-of-life version?
One major release at a time. MongoDB's upgrade documentation says that to upgrade to 8.0 you must already be running a 7.0-series release (upgrade 7.0 to 8.0). A deployment on 5.0 or earlier therefore passes through each intermediate major version.