MongoDB Server
DatabaseMongoDB Server 8.3 is the newest actively maintained release, currently at patch 8.3.8. 3 of 32 tracked cycles remain supported. The next cycle scheduled to reach end-of-life is 7.0, on August 31, 2027.
Support pattern
How MongoDB Server has behaved across the cycles tracked here, rather than what its policy documents state. Useful for judging how much runway a version is likely to have before you commit to it.
Support windows are getting shorter: the most recent cycles run about 27 months less than the earlier ones.
Computed from release and end-of-life dates tracked for MongoDB Server. Medians are used rather than averages so one unusually short or long release does not skew the figure. Cycles with no recorded end-of-life date are excluded from the support window.
How MongoDB versioning, EOL & security support work
MongoDB Server uses a major.minor.patch scheme, though the meaning of "minor" has evolved per MongoDB's own Software Support Policy. Starting with MongoDB 8.2, in-between builds became formal Minor Releases with their own place in the lifecycle schedule. A new major version still ships roughly once a year, and every patch release within a given major or minor series inherits that series' support window.
MongoDB accepts vulnerability reports through its published security disclosure channels, and confirmed issues are patched and shipped as ordinary patch releases within each supported series, tracked with CVE identifiers where applicable. Because support explicitly cuts off the moment a version passes its end-of-life date, a team left on an EOL server version stops receiving fixes even for actively exploited vulnerabilities.
Sources: MongoDB Software Support Policy, MongoDB Software Lifecycle Schedules
Release lifecycle
Get an email when MongoDB Server ships a release, announces an end-of-life date, or moves a date it already announced.
Get MongoDB Server alerts