CVE-2026-82075: CWE-770: Allocation of Resources Without Limits or Throttling in MongoDB MongoDB Server
An uncontrolled resource consumption weakness exists in the request-handling path of the MongoDB sharded-cluster router process. A client that has network access to a router port and has not authenticated can supply connection-monitoring parameters that cause the server to expend CPU resources without any rate limiting, degrading or denying service to legitimate clients. No authentication, elevated privileges, or user interaction is required. Only availability is affected; data confidentiality and integrity are not impacted.
AI Analysis
Technical Summary
This vulnerability (CWE-770) exists in the request-handling path of the MongoDB sharded-cluster router process. An unauthenticated client can supply connection-monitoring parameters that cause the server to consume excessive CPU resources without any throttling or rate limiting. This leads to denial of service by degrading the availability of the MongoDB server. The flaw requires no privileges or user interaction and solely impacts service availability. The affected versions explicitly identified are 7.0.0, 8.0.0, and 8.3.0. There is no vendor advisory or patch available at this time, and no known exploits in the wild have been reported.
Potential Impact
The vulnerability allows unauthenticated remote attackers to cause resource exhaustion on the MongoDB sharded-cluster router, resulting in denial of service conditions. This impacts the availability of the service but does not compromise data confidentiality or integrity. Legitimate clients may experience degraded performance or inability to connect due to excessive CPU consumption triggered by crafted connection-monitoring parameters.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, consider restricting network access to MongoDB router ports to trusted clients only and monitor for unusual connection-monitoring parameter usage. No official patch or temporary fix is currently available.
CVE-2026-82075: CWE-770: Allocation of Resources Without Limits or Throttling in MongoDB MongoDB Server
Description
An uncontrolled resource consumption weakness exists in the request-handling path of the MongoDB sharded-cluster router process. A client that has network access to a router port and has not authenticated can supply connection-monitoring parameters that cause the server to expend CPU resources without any rate limiting, degrading or denying service to legitimate clients. No authentication, elevated privileges, or user interaction is required. Only availability is affected; data confidentiality and integrity are not impacted.
CVSS v4.0
Score 8.7high
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) exists in the request-handling path of the MongoDB sharded-cluster router process. An unauthenticated client can supply connection-monitoring parameters that cause the server to consume excessive CPU resources without any throttling or rate limiting. This leads to denial of service by degrading the availability of the MongoDB server. The flaw requires no privileges or user interaction and solely impacts service availability. The affected versions explicitly identified are 7.0.0, 8.0.0, and 8.3.0. There is no vendor advisory or patch available at this time, and no known exploits in the wild have been reported.
Potential Impact
The vulnerability allows unauthenticated remote attackers to cause resource exhaustion on the MongoDB sharded-cluster router, resulting in denial of service conditions. This impacts the availability of the service but does not compromise data confidentiality or integrity. Legitimate clients may experience degraded performance or inability to connect due to excessive CPU consumption triggered by crafted connection-monitoring parameters.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, consider restricting network access to MongoDB router ports to trusted clients only and monitor for unusual connection-monitoring parameter usage. No official patch or temporary fix is currently available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mongodb
- Date Reserved
- 2026-08-27T22:54:06.052Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6aa03a2aacd9273b49ec3779
Added to database: 09/08/2026, 16:39:06 UTC
Last enriched: 09/08/2026, 16:52:12 UTC
Last updated: 09/09/2026, 00:23:22 UTC
Views: 9
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.