Chapter 1 · Practice 1 of 3
Run a supported MongoDB version and track end-of-life dates
Why it matters
Each MongoDB release has a published end-of-life date, after which it gets no fixes, including security fixes.
| Version | Released | End of life |
|---|---|---|
| 9.0 | September 2026 | October 31, 2031 |
| 8.3 | May 2026 | October 31, 2029 |
| 8.0 | October 2024 | October 31, 2029 |
| 7.0 | August 2023 | August 31, 2027 |
| 6.0 | July 2022 | Ended July 31, 2025 |
If you are on 6.0 or older, you are already unsupported. 7.0 reaches end of life in August 2027, so plan its upgrade now.
The MongoDB security checklist lists watching for CVEs, upgrading regularly and tracking end-of-life dates as ongoing production tasks. Managed services such as Atlas handle patching but still require you to move between major versions.
Do
- Check the lifecycle page when planning the year
- Apply patch releases within the same major version promptly
- Test the application against the next major version in staging