MongoDB 1.x — End of Life
EOLMongoDB 1.x — All releases
| Version | Released | Active support | EOL date | Latest patch | Status |
|---|---|---|---|---|---|
| 1.8 | Mar 16, 2011 | — | Sep 30, 2012 | 1.8.5 | EOL |
| 1.6 | Aug 5, 2010 | — | Feb 28, 2012 | 1.6.5 | EOL |
| 1.4 | Mar 25, 2010 | — | Sep 30, 2012 | 1.4.5 | EOL |
| 1.2 | Dec 10, 2009 | — | Jun 30, 2011 | 1.2.5 | EOL |
| 1.0 | Aug 27, 2009 | — | Aug 31, 2010 | 1.0.1 | EOL |
CVEs affecting MongoDB 1.x (0)
MongoDB 1.x is EOL — migrate to MongoDB 2.x
MongoDB 2.x is the next major release. Plan your upgrade before MongoDB 1.x stops receiving security patches.
Frequently asked questions
Is MongoDB 1 end of life?
Yes. All MongoDB 1.x releases have reached end of life and no longer receive security patches. Migrate to MongoDB 2.x as soon as possible.
What CVEs affect MongoDB 1?
No CVEs are currently tracked for MongoDB 1.x in our database. This may mean no vulnerabilities have been recorded yet, or the data is still syncing.
What is the latest MongoDB 1 version?
The latest MongoDB 1.x patch release is 1.8.5, released on February 1, 2012. Always run the latest patch to benefit from all security fixes.
How to migrate from MongoDB 1 to MongoDB 2?
To migrate from MongoDB 1 to MongoDB 2: (1) review the official MongoDB 2 migration guide for breaking changes, (2) update dependencies and configuration accordingly, (3) test thoroughly in a staging environment, (4) deploy with a rollback plan. Starting early gives you time to resolve compatibility issues before your current version reaches end of life.
Is it safe to run MongoDB 1 in production?
No. MongoDB 1 has reached end of life and security vulnerabilities are no longer patched. Upgrade to a supported version immediately.
Data sourced from endoflife.date · CVE data from NVD · EPSS from FIRST.org · KEV from CISA