Loading vulnerability…
CVE-2026-81521 is an improper input-validation vulnerability in the MongoDB Go Driver client-level bulk write API. Client.BulkWrite accepts a caller-supplied database name and uses it to construct the target namespace without escaping a reserved namespace-separator character. A database name containing that character can alter namespace parsing, causing bulk write operations to be directed to a database and collection other than the application intended. The issue is limited to the Client.BulkWrite API.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A write-redirection vulnerability in the MongoDB Go Driver caused by an unvalidated database name in Client.BulkWrite.
A write-redirection vulnerability in the MongoDB Go Driver due to an unvalidated database name in Client.BulkWrite.
A network-accessible, low-complexity vulnerability requiring low privileges that can cause high integrity impact. The content identifies Debian Linux 12.0, 13.0, and 14.0 and the golang-mongodb-mongo-driver package in its affected CPE information.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.