EOLCanaryEOLCanary
← Explore

MongoDB End of Life Dates

database

Database administrators and developers rely on MongoDB to manage and store data, and tracking its end-of-life dates is crucial for maintaining the security and integrity of their applications. MongoDB was created to solve the problem of scalable and flexible data storage, and it has been maintained by its community and the company behind it since its inception. The reason developers use MongoDB is its ability to handle large amounts of data and provide high performance, making it a popular choice for many applications. MongoDB has been around for a while, and its community has been actively maintaining and updating it to ensure it remains a secure and reliable choice for data storage.

The end-of-life landscape for MongoDB is complex, with a total of 32 versions, out of which 28 have already reached their end-of-life. Currently, there are 4 active versions, with the latest stable version being 7.0.32. The next version to reach its end-of-life is 8.2, which is scheduled to expire on 2026-07-31. This means that developers who are still using version 8.2 should start planning their upgrades to a newer version to ensure they continue to receive security patches and support. The last version to reach its end-of-life was 8.1, which expired on 2025-09-30, and developers who were using this version should have already upgraded to a newer version.

The security picture for MongoDB is relatively stable, with a total of 74 CVEs tracked, out of which none are critical. However, version 8.2 is the most affected, with 20 CVEs, which is a significant number. Although there are no critical CVEs, it is still important for developers to take action and upgrade to a newer version to ensure they have the latest security patches. Additionally, developers should regularly check the KEV status to ensure they are aware of any known vulnerabilities and take necessary actions to mitigate them. By staying on top of MongoDB's end-of-life dates and security patches, developers can ensure their applications remain secure and reliable.

Last updated: Jul 24, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
8.3 May 31, 2026—Oct 31, 2029in 1195d8.3.4Active
8.2 Sep 30, 2025—Jul 31, 2026in 7d8.2.11EOL soon
8.1 Jun 30, 2025—Sep 30, 2025297d ago8.1.3EOL
8.0 Oct 31, 2024—Oct 31, 2029in 1195d8.0.26Active
7.3 Mar 31, 2024—Oct 2, 2024660d ago7.3.4—EOL
7.2 Jan 31, 2024—Mar 27, 2024849d ago7.2.2—EOL
7.1 Oct 31, 2023—Jan 23, 2024913d ago7.1.1—EOL
7.0 Aug 31, 2023—Aug 31, 2027in 403d7.0.37Active
6.3 Apr 30, 2023—Aug 31, 20231058d ago6.3.2EOL
6.2 Feb 28, 2023—Apr 24, 20231187d ago6.2.1EOL
6.1 Oct 31, 2022—Feb 9, 20231261d ago6.1.1EOL
6.0 Jul 31, 2022—Jul 31, 2025358d ago6.0.29EOL
5.3 Mar 31, 2022—Jul 19, 20221466d ago5.3.2EOL
5.2 Jan 31, 2022—Mar 23, 20221584d ago5.2.1EOL
5.1 Nov 30, 2021—Jan 19, 20221647d ago5.1.1EOL
5.0 Jul 31, 2021—Oct 31, 2024631d ago5.0.34EOL
4.4 Jul 31, 2020—Feb 29, 2024876d ago4.4.31EOL
4.2 Aug 31, 2019—Apr 30, 20231181d ago4.2.25EOL
4.0 Jun 30, 2018—Apr 30, 20221546d ago4.0.28EOL
3.6 Nov 30, 2017—Apr 30, 20211911d ago3.6.23EOL
3.4 Nov 30, 2016—Jan 31, 20202366d ago3.4.24EOL
3.2 Dec 31, 2015—Sep 30, 20182854d ago3.2.22EOL
3.0 Mar 31, 2015—Feb 28, 20183068d ago3.0.15EOL
2.6 Apr 7, 2014—Oct 31, 20163553d ago2.6.12EOL
2.4 Mar 18, 2013—Mar 31, 20134863d ago2.4.14EOL
2.2 Aug 28, 2012—Feb 28, 20144529d ago2.2.7EOL
2.0 Sep 11, 2011—Mar 31, 20134863d ago2.0.9EOL
1.8 Mar 16, 2011—Sep 30, 20125045d ago1.8.5EOL
1.6 Aug 5, 2010—Feb 28, 20125260d ago1.6.5EOL
1.4 Mar 25, 2010—Sep 30, 20125045d ago1.4.5EOL
1.2 Dec 10, 2009—Jun 30, 20115503d ago1.2.5EOL
1.0 Aug 27, 2009—Aug 31, 20105806d ago1.0.1EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions