What is CVE-2026-81521?A high-severity flaw in Go Driver, explained.
CVE-2026-81521 is a high-severity flaw (CVSS 7.1) in Go Driver from Mongodb, published on 27 August 2026. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.2%. If you run an affected version, plan in the vendor’s fix.
Published 27 August 2026. Record last updated 6 October 2026. We keep this page's data up to date.
What is CVE-2026-81521? In plain terms.
It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything.
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.
What kind of flaw is it?
- CWE-99Improper Control of Resource Identifiers ('Resource Injection')
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstAn ordinary user account
- Does someone have to clickNo, nobody has to do anything
Severity vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Is CVE-2026-81521 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.2%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2026-81521 scores 23. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2026-81521 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2026-81521? One product.
The published record lists 1 product from 1 vendor. Versions are shown as published: "2.1.0 to before 2.8.2" means from 2.1.0 up to, but not including, 2.8.2. If you run one of these, check your version, then go to the fix below.
How do I fix CVE-2026-81521? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2026-81521 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The MongoDB Go Driver's client-level bulk write operation may accept a caller-supplied database name containing a reserved separator character without escapi...
- Matched to
- Go Driver on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2026-81521 is a high-severity flaw in Go Driver from Mongodb, published on 27 August 2026. It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything.
It scores 7.1 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2026-81521 is 23 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.2%. That can change at any time, which is why we keep watching.
For Go Driver from Mongodb: 2.1.0 to before 2.8.2.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.