CVE-2026-8336: Post-authentication use-after-free error in $_internalJsEmit and mapreduce commands

Published May 13, 2026
·
Updated

After invoking $internalJsEmit, which is not intended to be directly accessible, or mapreduce command’s map function in a certain way, an authenticated user can subsequently crash mongod when the server-side JavaScript engine (through $where, $function, mapreduce reduce stage, etc.) is used also in a specific way, resulting in a post-authentication denial-of-service.

This issue impacts MongoDB Server v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.

Affected Software

3 affected components
MongoDB MongoDB Server>=8.2.0<8.2.9, >=8.3.0<8.3.2
MongoDB MongoDB>=8.2.0<8.2.9
MongoDB MongoDB>=8.3.0<8.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade MongoDB Server to a version that resolves this vulnerability.

    Fixed in 8.2.9
  2. Upgrade

    Upgrade MongoDB Server to a version that resolves this vulnerability.

    Fixed in 8.3.2

Event History

May 13, 2026
CVE Published
via MITRE·12:16 AM
Data Sourced
via MITRE·12:16 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 AM
DescriptionSeverityWeaknessAffected Software
Jun 29, 58424
Event
via FIRST·05:13 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-8336?

CVE-2026-8336 has a severity rating that indicates it poses a significant risk due to a post-authentication use-after-free vulnerability that could crash the MongoDB server.

2

How do I fix CVE-2026-8336?

To fix CVE-2026-8336, upgrade to MongoDB server versions 7.0.34, 8.0.23, 8.2.9, or 8.3.2 or later, which contain the necessary patches.

3

Who is affected by CVE-2026-8336?

CVE-2026-8336 affects authenticated users of MongoDB Server versions prior to 7.0.34, 8.0.23, 8.2.9, and 8.3.2.

4

What impact does CVE-2026-8336 have on MongoDB Server?

The impact of CVE-2026-8336 is that it can allow authenticated users to crash the MongoDB server, potentially leading to service disruption.

5

Is there any workaround for CVE-2026-8336?

There are no recommended workarounds for CVE-2026-8336; the best mitigation is to apply updates to the MongoDB server as specified.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203