CVE-2026-11933
Use-after-free in MongoDB SSR JS can crash or memory-leak.
Is CVE-2026-11933 being exploited?
Not confirmed. CVE-2026-11933 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-11933?
CVE-2026-11933 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-11933?
Yes. A fix has been recorded for CVE-2026-11933. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-11933 affect?
CVE-2026-11933 affects MongoDB Server (mongod). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-11933?
Patch when available; restrict/disable server-side JS usage.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated read user can crash mongod or leak memory via server-side JavaScript ($where/$function).
Patch when possible
- affected>= 8.3.0 and <= 8.3.3
- affected>= 8.2.0 and <= 8.2.10
- affected>= 8.0.0 and <= 8.0.25
- affected>= 7.0.0 and <= 7.0.36
- affected>= 6.0 and <= 6.0.28
- affected>= 5.0 and <= 5.0.33
- affected>= 4.4.0 and <= 4.4.30
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.