Skip to content
Database

MongoDB Releases

Track every MongoDB release from latest stable to end-of-life. Version timelines, licensing context, Atlas vs self-hosted, upgrade paths, and driver compatibility.

Total Versions

Supported

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

5.0
6.0
7.0
8.0
2022 2023 2024 2025 2026 2027 2028 2029
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active / LTS
Maintenance
Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

5.0 6.0 Medium Difficulty
Est. 4-8 hours

Breaking Changes

  • Removed legacy opcounters
  • Change streams improvements (breaking for some drivers)
  • Queryable Encryption introduced
  • Cluster-to-cluster sync
  • Time series collections improvements

Migration Notes

Set FCV to 5.0 during upgrade, then advance to 6.0 after verification. Update all drivers to 6.0-compatible versions first. Test change stream consumers.

6.0 7.0 Medium Difficulty
Est. 4-8 hours

Breaking Changes

  • Removed legacy wire protocol opcodes (OP_QUERY, etc.)
  • Compound wildcard indexes
  • Sharding improvements
  • Atlas Search integration changes
  • Deprecated shell methods removed

Migration Notes

The wire protocol change is the biggest risk: very old drivers using OP_QUERY will break. Ensure all drivers are updated to versions that use OP_MSG. Follow the one-version-at-a-time rule.

7.0 8.0 Medium Difficulty
Est. 4-8 hours

Breaking Changes

  • Queryable Encryption v2 (not backward compatible)
  • New aggregation operators
  • Improved sharding performance
  • Atlas Vector Search integration

Migration Notes

If using Queryable Encryption v1, you must re-encrypt data. Standard upgrades follow the same FCV pattern. Update drivers first, upgrade secondaries, then primary.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version EOL Risk CVE Risk Ecosystem Cloud Support Overall Recommended Action
MongoDB 4.4 and below Critical High EOL Dropped Critical Past EOL — must upgrade (one version at a time)
MongoDB 5.0 Critical Medium EOL Legacy Critical EOL Oct 2024 — upgrade to 6.0 first, then 7.0+
MongoDB 6.0 High Low Maintenance Full High EOL Jul 2025 — plan upgrade to 7.0
MongoDB 7.0 Low Low Active Full Low Current stable — recommended
MongoDB 8.0 None Low Active Full Low Latest — adopt when ready

Risk combines EOL status, driver compatibility, security patches, and cloud provider alignment. Assessed as of March 2026.

Major Version Feature Comparison

Side-by-side feature differences across major versions.

Feature 5.0 6.0 7.0 8.0
Time series collections Stable Enhanced Enhanced Enhanced
Queryable Encryption No Preview Stable (v1) Stable (v2)
Change streams Stable Enhanced Enhanced Enhanced
Cluster-to-cluster sync No Stable Stable Stable
Wildcard indexes Basic Basic Compound Compound
Atlas Search Basic Improved Integrated Vector Search
Wire protocol Legacy+MSG Legacy+MSG MSG only MSG only
Sharding Stable Improved Improved Enhanced
License SSPL SSPL SSPL SSPL
Supported until Oct 2024 Jul 2025 Aug 2026 Sep 2027

Embed Badges

Add live MongoDB status badges to your README, docs, or dashboard.

Health Status

Overall support health

MongoDB Health Status
![MongoDB Health Status](https://img.releaserun.com/badge/health/mongodb.svg)

EOL Countdown

Next end-of-life date

MongoDB EOL Countdown
![MongoDB EOL Countdown](https://img.releaserun.com/badge/eol/mongodb.svg)

Latest Version

Current stable release

MongoDB Latest Version
![MongoDB Latest Version](https://img.releaserun.com/badge/v/mongodb.svg)

CVE Status

Known vulnerabilities

MongoDB CVE Status
![MongoDB CVE Status](https://img.releaserun.com/badge/cve/mongodb.svg)

Frequently Asked Questions

Common questions about MongoDB releases and lifecycle.

How long are MongoDB versions supported?
MongoDB provides roughly 30 months of support for each major release under the Server Side Public License (SSPL). Lifecycle support includes bug fixes, security patches, and driver compatibility updates.
What is the MongoDB SSPL license?
MongoDB switched from AGPL to SSPL in October 2018. SSPL requires that anyone offering MongoDB as a service must open-source their entire service stack. This effectively prevents cloud providers from offering managed MongoDB without a commercial license. Self-hosted use is unaffected.
MongoDB Atlas vs self-hosted: which should I choose?
Atlas handles backups, scaling, security, and upgrades. Self-hosted gives you full control and avoids vendor lock-in. For most teams, Atlas is the right choice unless you have specific compliance requirements or want to avoid the SSPL. Atlas is available on AWS, GCP, and Azure.
Should I use MongoDB or PostgreSQL?
PostgreSQL with JSONB handles most document-style workloads well and gives you relational capabilities too. MongoDB excels at truly schemaless data, horizontal scaling (sharding), and real-time analytics. Choose MongoDB if your data is genuinely schemaless and you need easy horizontal scaling. Choose PostgreSQL for everything else.
How hard is it to upgrade MongoDB?
MongoDB only supports upgrading one major version at a time (e.g., 6.0→7.0, not 5.0→7.0). Set the feature compatibility version (FCV) before upgrading. Replica sets and sharded clusters must follow specific node-by-node upgrade procedures. Always test with your specific driver versions.

Related Tools

Browse All Version History