Quick answers
- Is CVE-2026-81520 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81520 being exploited in the wild.
- How severe is CVE-2026-81520?
- High severity, with a CVSS score of 7.5, published 28 August 2026.
- Which products and versions are affected?
- MongoDB Connector for BI.
- Is there a fix for CVE-2026-81520?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-81520 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-81520?
- Check whether you run MongoDB Connector for BI. 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
This is a denial-of-service vulnerability in MongoDB Connector for BI's SASL authentication handler. An unauthenticated client on the network can initiate a SASL login exchange and then deliberately not complete it, causing the server to hold the connection indefinitely. The root cause is the absence of a timeout on the overall negotiation loop and no read deadline on client communications. Each incomplete session occupies a worker thread, client connection slot, and associated backend database connections. By repeated exploitation, an attacker can exhaust the configured connection pool and prevent legitimate users from establishing sessions. Patches are available in updated release notes documented by MongoDB.
Affected products
- MongoDB Connector for BI
Timeline
- 2026-08-28: published
- 2026-08-28: disclosed