Affects MongoDB's sharded-cluster router (widely deployed); unauthenticated resource-exhaustion can disrupt production services and cluster availability.
CVE-2026-82075
Unauthenticated resource-exhaustion DoS against MongoDB sharded router (mongos).
Is CVE-2026-82075 being exploited?
Not confirmed. CVE-2026-82075 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.52% probability of exploitation in the next 30 days.
How severe is CVE-2026-82075?
CVE-2026-82075 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-82075?
Yes. A fix has been recorded for CVE-2026-82075. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82075 affect?
CVE-2026-82075 affects MongoDB mongos (sharded-cluster router), Sharded MongoDB deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82075?
Block/limit access to mongos, implement rate-limiting/ingress filters, monitor traffic; apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can supply conn-monitoring params to exhaust CPU on mongos, degrading or denying service to clients.
Immediate action required
- affected>= 7.0.0 and < 7.0.41
- affected>= 8.0.0 and < 8.0.30
- affected>= 8.3.0 and < 8.3.9
- affected>= 8.3.0 and < 8.3.9
- affected>= 8.0.0 and < 8.0.30
- affected>= 7.0.0 and < 7.0.41
As published in the CVE Program record, and, for products that ship the affected component, in the advisory named beside them. 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.