MongoDB 7.3 (Rapid Release) · Version Status
MongoDB 7.3 (Rapid Release) End of Life Date
MongoDB 7.3 (Rapid Release) end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
MongoDB 7.3 (Rapid Release) is past end of life. This version no longer receives security patches. 708 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 2, 2024
708 days past EOL
Latest Release
7.3.4
Standard release
Release Date
Mar 31, 2024
MongoDB 7.3 (Rapid Release) series
Lifecycle detail
MongoDB 7.3 was released on March 31, 2024 and support ended on October 2, 2024 — a supported lifespan of 6 months, shorter than the 1 year and 7 months median for MongoDB releases. The last patch it will ever receive is 7.3.4, published August 14, 2024 — 2 months before support ended. It has been without security patches for 1 year and 11 months. 4 newer MongoDB releases have shipped since.
Attack Surface
30/30 Critical tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended MongoDB 7.3 (Rapid Release) support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.1 |
Aug 31, 2010 |
EOL |
| 1.2 |
1.2.5 |
Jun 30, 2011 |
EOL |
| 1.4 |
1.4.5 |
Sep 30, 2012 |
EOL |
| 1.6 |
1.6.5 |
Feb 28, 2012 |
EOL |
| 1.8 |
1.8.5 |
Sep 30, 2012 |
EOL |
| 2.0 |
2.0.9 |
Mar 31, 2013 |
EOL |
| 2.2 |
2.2.7 |
Feb 28, 2014 |
EOL |
| 2.4 |
2.4.14 |
Mar 31, 2013 |
EOL |
What does MongoDB 7.3 (Rapid Release) end of life mean?
When MongoDB 7.3 (Rapid Release) reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running MongoDB 7.3 (Rapid Release) past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to MongoDB 8.3 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does MongoDB 7.3 (Rapid Release) reach end of life?
MongoDB 7.3 (Rapid Release) reached end of life on October 2, 2024. This version is no longer receiving security patches.
Is MongoDB 7.3 (Rapid Release) still supported?
No. MongoDB 7.3 (Rapid Release) reached end of life on October 2, 2024 and is no longer receiving security patches.
What should I upgrade to from MongoDB 7.3 (Rapid Release)?
The recommended upgrade from MongoDB 7.3 (Rapid Release) is
MongoDB 8.3 — the latest actively supported version. Check the
MongoDB full timeline for all supported versions.
What are the security risks of running MongoDB 7.3 (Rapid Release) past EOL?
When MongoDB 7.3 (Rapid Release) reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL MongoDB should migrate immediately or implement compensating controls.