[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fotl8F78dOkQywLhhvcmkFyLvuVlmqSJvOigtidh3YW0":3},{"product":4,"cycleMajor":14,"releases":15,"cves":25,"nextMajor":9,"indexable":34},{"id":5,"slug":6,"name":7,"category":8,"vendor":9,"description":10,"logo_url":11,"official_url":9,"synced_at":12,"created_at":13},"192a985c-4b85-435a-af09-a99917018d8d","mongodb","MongoDB","database",null,"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.\n\nThe 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.\n\nThe 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.","https:\u002F\u002Fcdn.simpleicons.org\u002Fmongodb","2026-10-07T02:00:12.129+00:00","2026-05-30T16:23:55.904463+00:00","9",[16],{"id":17,"product_id":5,"cycle":18,"release_date":19,"eol":20,"eol_boolean":9,"latest":21,"latest_release_date":22,"lts":23,"support":9,"created_at":24},"9204a6ab-4fa5-4ac7-8378-c5eb8cd42f68","9.0","2026-09-30","2031-10-31","9.0.2","2026-09-28",false,"2026-10-01T02:00:13.211388+00:00",[26],{"cveId":27,"releaseId":17,"cycle":18,"description":28,"severity":29,"cvssScore":30,"epssScore":31,"inKev":23,"publishedAt":32,"url":33},"CVE-2026-9737","During query planning when reading the sort pattern in raw BSONObj form, in some places we don’t explicitly handle the meta expression case. This may lead to incorrect transformations leading to invariant failure.","MEDIUM",6.5,0.0042,"2026-07-22T20:17:09.863+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-9737",true]