Quick answers
- Is CVE-2026-120822 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120822 being exploited in the wild.
- How severe is CVE-2026-120822?
- Medium severity, with a CVSS score of 6.7, published 10 November 2026.
- Which products and versions are affected?
- MongoDB Server 7.0.40+, 8.0.29+, 8.3.8+, 9.0.0+.
- Is there a fix for CVE-2026-120822?
- Yes: fixed in 8.3.16, 9.0.7, 8.0.37, 7.0.48. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120822 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-120822?
- Check whether you run MongoDB Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 8.3.16, 9.0.7, 8.0.37, 7.0.48
Technical details
The applyOps command omits a UUID-targeted authorization check when the oplogApplicationMode parameter is set to a non-default value (Secondary, InitialSync, or Recovering) by the client, allowing an authenticated user to bypass the check introduced in SERVER-130139. An attacker with cluster applyOps and useUUID privileges can specify a UUID resolving to a collection they lack rights on and perform unauthorized drop, collMod, dropIndexes, or renameCollection operations. The vulnerability affects all releases carrying the SERVER-130139 fix.
Affected products
- MongoDB Server 7.0.40+, 8.0.29+, 8.3.8+, 9.0.0+
Timeline
- 2026-11-10: disclosed