Quick answers
- Is CVE-2026-120808 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120808 being exploited in the wild.
- How severe is CVE-2026-120808?
- High severity, with a CVSS score of 7.4, published 10 November 2026.
- Which products and versions are affected?
- MongoDB 7.0 before 7.0.48, 8.0 before 8.0.37, 8.2, 8.3 before 8.3.16, 9.0 before 9.0.7.
- Is there a fix for CVE-2026-120808?
- Yes: fixed in 7.0.48, 8.0.37, 8.3.16, 9.0.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120808 attacked?
- It is attacked over the network or from the adjacent network, in a software library.
- Am I affected by CVE-2026-120808?
- Check whether you run MongoDB 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: 7.0.48, 8.0.37, 8.3.16, 9.0.7
Technical details
The vulnerability exists in MongoDB's Apple SecureTransport TLS backend where the result of SecTrustEvaluate is discarded for IPv6-addressed peers, bypassing certificate chain-of-trust validation. An on-path attacker can exploit this by presenting a self-signed certificate with the target's IPv6 address in the Subject Alternative Name to intercept encrypted traffic. The issue affects only macOS systems and has been patched in versions 7.0.48, 8.0.37, 8.3.16, and 9.0.7.
Affected products
- MongoDB MongoDB 7.0 before 7.0.48, 8.0 before 8.0.37, 8.2, 8.3 before 8.3.16, 9.0 before 9.0.7
Timeline
- 2026-11-10: disclosed