MongoDB Server 1.8
MongoDB Server 1.8
The MongoDB Server 1.8 reached end of service life on Sep 30, 2012 — MongoDB Server no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your MongoDB Server 1.8 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- mongodb
- release
- 1.8
- product Label
- MongoDB Server
- release Label
- 1.8
- codename
- lts
- latest Version
- 1.8.5
- release Date
- 2011-03-16
- maintained
- source Url
- https://endoflife.date/mongodb
Lifecycle Dates
- End of Service Life
- Sep 30, 2012
- Last OEM Support
- Sep 30, 2012
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for MongoDB Server 1.8 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for MongoDB Server 1.8?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for MongoDB Server 1.8 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
MongoDB Server 1.8 Support: Frequently Asked Questions
Is the MongoDB Server 1.8 still supported?
MongoDB Server ended support for the MongoDB Server 1.8 on Sep 30, 2012 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the MongoDB Server 1.8 end of service life (EOSL) date?
MongoDB Server lists the end of service life for the MongoDB Server 1.8 as Sep 30, 2012.
Can I keep using the MongoDB Server 1.8 after its EOSL date?
Yes. EOSL means MongoDB Server stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the MongoDB Server 1.8 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting MongoDB Server 1.8
8 published CVEs affect the MongoDB Server 1.8, including 1 rated critical or high severity. MongoDB Server no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2026-9753 | HIGH | 7.2 | Jun 9, 2026 | The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command. |
| CVE-2012-6619 | MEDIUM | 6.4 | Mar 6, 2014 | The default configuration for MongoDB before 2.3.2 does not validate objects, which allows remote authenticated users to cause a denial of service (crash) or read system memory via a crafted BSON object in the column name in an insert command, which triggers a buffer over-read. |
| CVE-2013-1892 | MEDIUM | 6.0 | Oct 1, 2013 | MongoDB before 2.0.9 and 2.2.x before 2.2.4 does not properly validate requests to the nativeHelper function in SpiderMonkey, which allows remote authenticated users to cause a denial of service (invalid memory access and server crash) or execute arbitrary code via a crafted memory address in the first argument. |
| CVE-2014-8180 | MEDIUM | 5.5 | Jun 6, 2017 | MongoDB on Red Hat Satellite 6 allows local users to bypass authentication by logging in with an empty password and delete information which can cause a Denial of Service. |
| CVE-2016-6494 | MEDIUM | 5.5 | Oct 3, 2016 | The client in MongoDB uses world-readable permissions on .dbshell history files, which might allow local users to obtain sensitive information by reading these files. |
| CVE-2015-1609 | MEDIUM | 5.0 | Mar 30, 2015 | MongoDB before 2.4.13 and 2.6.x before 2.6.8 allows remote attackers to cause a denial of service via a crafted UTF-8 string in a BSON request. |
| CVE-2017-2665 | MEDIUM | 4.8 | Jul 6, 2018 | The skyring-setup command creates random password for mongodb skyring database but it writes password in plain text to /etc/skyring/skyring.conf file which is owned by root but read by local user. Any local user who has access to system running skyring service will be able to get password in plain text. |
| CVE-2013-2132 | MEDIUM | 4.3 | Aug 15, 2013 | bson/_cbsonmodule.c in the mongo-python-driver (aka. pymongo) before 2.5.2, as used in MongoDB, allows context-dependent attackers to cause a denial of service (NULL pointer dereference and crash) via vectors related to decoding of an "invalid DBRef." |