MongoDB Ops Manager 8.0.27 Fixes Three Authorization and Availability Vulnerabilities
Tech GuruQuick Answer
The authority published CVE-2026-87108 for MongoDB Ops Manager 7.0 and 8.0. MongoDB disclosed cross-project monitoring-record access by a read-only user, exposure of pending MFA enrollment seeds to another organization member, and unauthenticated resource consumption through monitoring endpoints. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory MongoDB Ops Manager 7.0 and 8.0, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-10-09 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | MongoDB Ops Manager 7.0 and 8.0 |
|---|---|
| Advisory | CVE-2026-87108 / CVE-2026-87109 / CVE-2026-87110 |
| CVEs | CVE-2026-87108, CVE-2026-87109, CVE-2026-87110 |
| Authoritative release date | 2026-10-09 05:52:14.194 UTC |
| Authority revision date | 2026-10-09 05:56:06.397 UTC |
| Affected versions | Ops Manager 7.0.0 through 7.0.23 and Ops Manager 8.0.0 through versions before 8.0.27. |
| Fixed version | Ops Manager 8.0.27 or later; obtain supported vendor direction for affected 7.0 deployments because the authority does not identify a fixed 7.0 build |
| CVSS base score | 2.3 / 6.0 / 6.9 (CVSS v4.0) |
| CVSS severity | Low to Medium |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
MongoDB disclosed cross-project monitoring-record access by a read-only user, exposure of pending MFA enrollment seeds to another organization member, and unauthenticated resource consumption through monitoring endpoints.
What To Validate Now
- Inventory. Locate MongoDB Ops Manager 7.0 and 8.0 deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: Ops Manager 7.0.0 through 7.0.23 and Ops Manager 8.0.0 through versions before 8.0.27. Do not infer applicability from product family or severity alone.
- Remediate. Apply Ops Manager 8.0.27 or later; obtain supported vendor direction for affected 7.0 deployments because the authority does not identify a fixed 7.0 build through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Restrict Ops Manager web-port access while upgrading, review pending MFA enrollments and user-listing access, and inspect monitoring-endpoint load. Do not claim a fixed 7.0 build absent vendor guidance. Preserve access, configuration, upgrade, and validation evidence.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
