Question 1

What is the EOL Risk Score for MongoDB 2.0?

Accepted Answer

MongoDB 2.0 has an EOL Risk Score™ of 90 out of 100, placing it in the Critical risk band. The score is calculated from four factors: EOL Recency (40/40), Attack Surface (30/30), CISA KEV Exposure (20/20), and Extended Support Availability (0/10).

Question 2

Is MongoDB 2.0 still supported?

Accepted Answer

MongoDB 2.0 is no longer supported — it has passed its end of life date (March 31, 2013). No further security patches will be issued. Upgrade to a supported version or obtain extended lifecycle support.

Question 3

When does MongoDB 2.0 reach end of life?

Accepted Answer

MongoDB 2.0 reached (or will reach) end of life on March 31, 2013. After this date, no security patches or bug fixes are issued by the vendor.

Question 4

What are the security risks of running MongoDB 2.0 after end of life?

Accepted Answer

After end of life, MongoDB 2.0 no longer receives security patches. Any newly discovered CVEs remain unpatched indefinitely. Organizations running EOL software also face compliance violations under SOC 2, PCI DSS, HIPAA, and ISO 27001, which require use of supported software versions.