A user with basic read-tier database privileges can use an option on a server-side data-change notification feature to
Source GCVE Database
Not known to be exploited · CVSS 2.3 Low · fixed in 9.0.7 : update MongoDB Server when convenient.
Data as of 10 Nov 2026, 22:37 UTC
Thin evidence
One scorer or none| CNA (mongodb) | CVSS 4.0 | 2.3 |
|---|---|---|
| CNA (mongodb) | CVSS 3.1 | 4.3 |
- Patch
- Available – fixed in 9.0.7, 8.3.16, 8.0.37 +1
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade MongoDB Server to 9.0.7, 8.3.16, 8.0.37 or 7.0.48.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MongoDBMongoDB Server | Affected
| Fixed in
|
| MongoDBMongoDB Server | Affected
| Fixed in
|
| MongoDBMongoDB Server | Affected
| Fixed in
|
| MongoDBMongoDB Server | Affected
| Fixed in
|
AI-suggested
Since the vulnerability arises from insufficient privilege checks in the notification feature, users should avoid using this feature with untrusted accounts until a fix is available. No additional permissions are required to exploit this issue, so restricting read-tier privileges or disabling the notification feature may reduce risk.
Description
A vulnerability exists where a user with basic read-tier database privileges can exploit a server-side data-change notification feature to access contents of certain restricted internal collections. This occurs because the privilege check only considers the target namespace and ignores the option that allows access to these internal collections. As a result, users can gain unintended read access to data they are normally denied when attempting direct reads.