Quick answers
- Is CVE-2026-115929 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115929 being exploited in the wild.
- How severe is CVE-2026-115929?
- Medium severity, with a CVSS score of 6.8, published 24 October 2026.
- Which products and versions are affected?
- MongoDB Compass before 1.53.1.
- Is there a fix for CVE-2026-115929?
- Yes: fixed in Compass 1.53.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115929 attacked?
- It is attacked over the network or from the adjacent network, in a software library.
- Am I affected by CVE-2026-115929?
- Check whether you run MongoDB Compass 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: Compass 1.53.1
Technical details
Electron's bundled TLS root certificate store includes recovered eMudhra intermediate certificates whose private keys were compromised, allowing arbitrary HTTPS certificate forging. An attacker with network-level access (adjacent network or internet interception) could perform man-in-the-middle attacks on Compass connections. The vulnerability is resolved by upgrading to Compass 1.53.1, which includes patched Electron 44.9.1.
Affected products
- MongoDB Compass before 1.53.1
Timeline
- 2026-10-20: disclosed
- 2026-10-23: patched