Quick answers
- Is CVE-2026-82071 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82071 being exploited in the wild.
- How severe is CVE-2026-82071?
- High severity, with a CVSS score of 8.1, published 8 September 2026.
- Which products and versions are affected?
- MongoDB Server 7.0 before 7.0.41, 8.0 before 8.0.30, 8.2 before 8.2.13, 8.3 before 8.3.9.
- Is there a fix for CVE-2026-82071?
- A patch was published on 2026-09-08: Fixes released in versions 7.0.41, 8.0.30, 8.2.13, 8.3.9, 9.0.0-rc2, 9.1.0-rc0, and later Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82071 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-82071?
- Check whether you run MongoDB. 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.
Technical details
The vulnerability exists in insufficient validation of storage engine configuration options, specifically in the handling of "source" and "import" strings in WiredTiger configuration. An authenticated user with write privileges can supply crafted parameters during collection creation that override internal storage metadata. This results in an out-of-bounds memory write in the server process. The attack requires authentication and write privileges, with attack vector being network-accessible MongoDB instances. Patches are available in versions 7.0.41, 8.0.30, 8.2.13, 8.3.9, 9.0.0-rc2, 9.1.0-rc0, and later.
Affected products
- MongoDB Server 7.0 before 7.0.41, 8.0 before 8.0.30, 8.2 before 8.2.13, 8.3 before 8.3.9
Timeline
- 2026-09-08: disclosed: CVE-2026-82071 published
- 2026-09-08: patched: Fixes released in versions 7.0.41, 8.0.30, 8.2.13, 8.3.9, 9.0.0-rc2, 9.1.0-rc0, and later