CVE-2026-8202: DoS in MongoDB Server 7.0-8.3.2
Plattform
mongodb
Komponente
mongodb
Behoben in
8.3.2
CVE-2026-8202 is a denial-of-service (DoS) vulnerability affecting MongoDB Server. An authenticated user, possessing aggregation permissions, can trigger a CPU exhaustion condition by crafting specific inputs to the $trim, $ltrim, and $rtrim aggregation operators. This results in sustained 100% CPU utilization, effectively rendering the MongoDB server unresponsive. The vulnerability impacts MongoDB Server versions 7.0.0 through 8.3.2 and is resolved in version 8.3.2.
Auswirkungen und Angriffsszenarien
The primary impact of CVE-2026-8202 is a denial-of-service. A successful exploitation can completely halt MongoDB server operations, preventing legitimate users from accessing data and applications relying on the database. This can lead to significant downtime and disruption of business processes. While the vulnerability requires authentication, the ease of crafting the malicious input makes it a relatively low-effort attack. The blast radius is limited to the affected MongoDB instance, but the impact can be severe if the database is critical to operations. There are no known precedents for this specific exploitation pattern, but similar CPU exhaustion vulnerabilities have historically led to significant service outages.
Ausnutzungskontext
CVE-2026-8202 was published on 2026-05-13. The vulnerability's severity is assessed as Medium (CVSS 4.3). No public proof-of-concept exploits are currently known. The EPSS score is pending evaluation. There are no indications of active exploitation campaigns targeting this vulnerability at this time. Refer to the MongoDB security advisory for further details.
Bedrohungsanalyse
Exploit-Status
CVSS-Vektor
Was bedeuten diese Metriken?
- Attack Vector
- Netzwerk — aus der Ferne über das Internet ausnutzbar. Kein physischer oder lokaler Zugriff erforderlich.
- Attack Complexity
- Niedrig — keine besonderen Bedingungen erforderlich. Zuverlässig ausnutzbar.
- Privileges Required
- Niedrig — jedes gültige Benutzerkonto ist ausreichend.
- User Interaction
- Keine — automatischer und lautloser Angriff. Das Opfer tut nichts.
- Scope
- Unverändert — Auswirkung auf das anfällige Komponente beschränkt.
- Confidentiality
- Keine — kein Vertraulichkeitseinfluss.
- Integrity
- Keine — kein Integritätseinfluss.
- Availability
- Niedrig — partieller oder intermittierender Denial of Service.
Betroffene Software
Schwachstellen-Klassifikation (CWE)
Zeitleiste
- Veröffentlicht
Mitigation und Workarounds
The primary mitigation for CVE-2026-8202 is to upgrade MongoDB Server to version 8.3.2 or later. If immediate upgrading is not possible, consider implementing temporary workarounds. Restricting aggregation permissions to only necessary users can limit the attack surface. Monitoring CPU utilization on the MongoDB server is crucial; unusual spikes could indicate exploitation attempts. Web Application Firewalls (WAFs) or proxies might be configured to inspect and block suspicious aggregation queries, although this is complex and may impact legitimate traffic. After upgrading, confirm the fix by attempting to reproduce the vulnerability with the original malicious input; CPU utilization should remain normal.
So behebenwird übersetzt…
Actualice su instancia de MongoDB Server a la versión 7.0.34, 8.0.23, 8.2.9 o 8.3.2 o superior para mitigar la vulnerabilidad. Esta actualización aborda el problema de agotamiento de la CPU al aplicar las operaciones de recorte en agregaciones con máscaras de caracteres densamente pobladas.
Häufig gestellte Fragen
What is CVE-2026-8202?
It's a denial-of-service vulnerability in MongoDB Server allowing authenticated users to exhaust CPU resources using specific aggregation operators.
Am I affected?
If you're running MongoDB Server versions 7.0.0 through 8.3.2, you are potentially affected. Upgrade to 8.3.2 to resolve the issue.
How to fix it?
Upgrade MongoDB Server to version 8.3.2 or later. Restricting aggregation permissions can offer temporary protection.
Is it being exploited?
Currently, there are no known public exploits or active campaigns targeting this vulnerability.
Where can I learn more?
Refer to the official MongoDB security advisory for detailed information and updates: [https://www.mongodb.com/docs/manual/release-notes/8.3.2/](https://www.mongodb.com/docs/manual/release-notes/8.3.2/)
Ist dein Projekt betroffen?
Lade deine Abhängigkeitsdatei hoch und erfahre sofort, ob dich diese und andere CVEs treffen.
Jetzt testen — kein Konto
Laden Sie ein Manifest hoch (composer.lock, package-lock.json, WordPress Plugin-Liste…) oder fügen Sie Ihre Komponentenliste ein. Sie erhalten sofort einen Schwachstellenbericht. Das Hochladen einer Datei ist nur der Anfang: Mit einem Konto erhalten Sie kontinuierliche Überwachung, Slack/email-Benachrichtigungen, Multi-Projekt- und White-Label-Berichte.
Abhängigkeitsdatei hier ablegen
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...