Quick answers
- Is CVE-2026-81523 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81523 being exploited in the wild.
- How severe is CVE-2026-81523?
- Medium severity, with a CVSS score of 4.4, published 27 August 2026.
- Which products and versions are affected?
- MongoDB Libmongocrypt prior to 1.20.3 and 1.21.0.
- Is there a fix for CVE-2026-81523?
- A patch was published on 2026-08-27: Fixed in libmongocrypt 1.20.3 and 1.21.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-81523 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-81523?
- Check whether you run MongoDB Libmongocrypt 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.
Technical details
A missing input-validation vulnerability exists in MongoDB libmongocrypt's automatic-encryption context initialization. The library accepts caller-supplied database identifiers without sanitization, specifically failing to reject database names containing dots (.) or embedded NUL bytes. This allows an attacker to specify an invalid database name that causes the library to select an incorrect encryption schema, potentially leading to data encrypted with the wrong key or schema. The vulnerability is exploitable by any code that calls the affected libmongocrypt API with untrusted database identifier input. MongoDB released patches in versions 1.20.3 and 1.21.0 that validate database and collection names against prohibited characters.
Affected products
- MongoDB libmongocrypt prior to 1.20.3 and 1.21.0
Timeline
- 2026-08-27: disclosed: CVE-2026-81523 published
- 2026-08-27: patched: Fixed in libmongocrypt 1.20.3 and 1.21.0