CVE-2026-13074: CWE-770: Allocation of Resources Without Limits or Throttling in MongoDB MongoDB Server
An unauthenticated remote client can cause excessive CPU consumption on a MongoDB server by sending a specific combination of parameters to the awaitable hello command in exhaust mode. The server's handling of this combination results in a response loop that bypasses normal throttling, allowing a small number of connections to degrade server availability.
AI Analysis
Technical Summary
This vulnerability (CWE-770) in MongoDB Server involves allocation of resources without limits or throttling. An unauthenticated remote client can exploit the awaitable hello command in exhaust mode by sending a crafted parameter combination that causes the server to enter a response loop. This loop bypasses normal throttling controls, resulting in excessive CPU usage and potential degradation of server availability. The affected versions explicitly include 7.0, 8.0, 8.2.0, and 8.3.0. No official patch or remediation level has been published yet, and no known exploits are reported in the wild as of the publication date.
Potential Impact
The vulnerability allows unauthenticated remote attackers to cause excessive CPU consumption on affected MongoDB servers, potentially degrading server availability and impacting service reliability. This can be achieved with a small number of connections due to bypassing of throttling mechanisms. There is no indication of data compromise or privilege escalation from the provided information.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or remediation level is provided, administrators should monitor MongoDB server usage patterns and consider implementing network-level protections such as rate limiting or firewall rules to restrict access to the awaitable hello command if possible. Avoid exposing MongoDB servers directly to untrusted networks until a fix is available.
CVE-2026-13074: CWE-770: Allocation of Resources Without Limits or Throttling in MongoDB MongoDB Server
Description
An unauthenticated remote client can cause excessive CPU consumption on a MongoDB server by sending a specific combination of parameters to the awaitable hello command in exhaust mode. The server's handling of this combination results in a response loop that bypasses normal throttling, allowing a small number of connections to degrade server availability.
CVSS v4.0
Score 6.9medium
Affected software
pkg:github/mongodb/mongoRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CWE-770) in MongoDB Server involves allocation of resources without limits or throttling. An unauthenticated remote client can exploit the awaitable hello command in exhaust mode by sending a crafted parameter combination that causes the server to enter a response loop. This loop bypasses normal throttling controls, resulting in excessive CPU usage and potential degradation of server availability. The affected versions explicitly include 7.0, 8.0, 8.2.0, and 8.3.0. No official patch or remediation level has been published yet, and no known exploits are reported in the wild as of the publication date.
Potential Impact
The vulnerability allows unauthenticated remote attackers to cause excessive CPU consumption on affected MongoDB servers, potentially degrading server availability and impacting service reliability. This can be achieved with a small number of connections due to bypassing of throttling mechanisms. There is no indication of data compromise or privilege escalation from the provided information.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or remediation level is provided, administrators should monitor MongoDB server usage patterns and consider implementing network-level protections such as rate limiting or firewall rules to restrict access to the awaitable hello command if possible. Avoid exposing MongoDB servers directly to untrusted networks until a fix is available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mongodb
- Date Reserved
- 2026-06-23T18:00:19.050Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6123209c2644c7f89b2cd2
Added to database: 07/22/2026, 20:08:00 UTC
Last enriched: 07/22/2026, 20:23:12 UTC
Last updated: 07/23/2026, 03:45:03 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.