This page was not yet optimized for use on mobile devices.
CVE-2026-11933
Data
| Vulnerability ID | CVE-2026-11933 |
|---|---|
| Published on | 12.06.2026 02:16 |
| Severity | HIGH |
Vulnerable configurations
- cpe:2.3:a:mongodb:mongodb:4.4.30:*:*:*:-:-:*:*
- cpe:2.3:a:mongodb:mongodb:5.0.32:*:*:*:-:-:*:*, cpe:2.3:a:mongodb:mongodb:5.0.33:*:*:*:-:-:*:*
-
cpe:2.3:a:mongodb:mongodb:6.0.0:-:*:*:-:*:*:*,
cpe:2.3:a:mongodb:mongodb:6.0.0:alpha:*:*:-:*:*:*,
cpe:2.3:a:mongodb:mongodb:6.0.0:alpha0:*:*:-:*:*:*,
cpe:2.3:a:mongodb:mongodb:6.0.0:alpha1:*:*:-:*:*:*,
cpe:2.3:a:mongodb:mongodb:6.0.0:rc0:*:*:-:*:*:*,
cpe:2.3:a:mongodb:mongodb:6.0.0:rc1:*:*:-:*:*:*,
cpe:2.3:a:mongodb:mongodb:6.0.0:rc10:*:*:-:*:*:*,
…
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.