CVE•Published 2026-08-27•Modified 2026-10-06•0 articles on news•4 live references•NVD data
CVE-2026-81521Mongodb · Go_driver
Vulnerability data via NVD (ingested)
CVSS v3.1
6.5
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS percentile
27
Exploit Prediction Scoring System · top 73% of all CVEs
Description
The MongoDB Go Driver's client-level bulk write operation may accept a caller-supplied database name containing a reserved separator character without escaping it before the name is used to build the target namespace for the operation. An application that passes untrusted input as a database name could therefore have the write directed at a database and collection other than the ones it intended. Only the Client.BulkWrite API is affected.
Timeline
Published 2026-08-27
Modified 2026-10-06
External references
Search for exposed instances
Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).
Shodan · vuln tag0 hosts
vuln:CVE-2026-81521Hosts Shodan has explicitly fingerprinted as vulnerable.
Shodan · product
product:"Mongodb Go Driver"All exposed Mongodb Go Driver instances — cross-reference with the CVE's affected-version range.
Shodan · banner/body mention
http.html:"Go Driver"HTTP body or banner mentions "Go Driver" — catches deploys Shodan didn't identify as a product.
More intel sources (5)
Shodan report
vuln:CVE-2026-81521Country / ASN / product breakdown for the vuln query.
Censys
vulnerabilities.cve_id: CVE-2026-81521Censys host search filtered to this CVE id.
grep.app
CVE-2026-81521Public source-code mentions — fast PoC discovery.
GitHub code
CVE-2026-81521GitHub code search for direct mentions.
Google dork
"CVE-2026-81521" exploit -site:nvd.nist.govWrite-ups and news, NVD excluded.
Known PoCs on GitHub
No public proof-of-concept repositories found for CVE-2026-81521 on GitHub.
We haven't classified any articles referencing CVE-2026-81521 yet. The external references above still apply.