vciy

Mongodb server, allocation of resources without limits or throttling: 4 records, one defect family

Mongodb server has been reported 4 separate times for the same kind of mistake, CWE-770, all published on 2026-07-22. A defect family is our own grouping of the CVE corpus: every record naming one product and one weakness class, collected so a repeat is visible as a repeat. No public source publishes this, and what this page counts is how often this one product has gone wrong in this one way.

What this page is, and what it is not

The records are public. This grouping is not. No source publishes defect families, so we built them: every record in the corpus sorted by the product an authority named and the weakness class carried with it, 21316 families over 105586 records. This one holds every record that names Mongodb server and carries CWE-770, matched character for character. We show the join because a grouping you cannot check is a grouping you should not cite.

That is 4 filings, all published on 2026-07-22, landing on the same weakness class in the same product. At this count it is a repeat rather than a pattern, and the roster below is short enough to read in full. This is what we held on 2026-09-20.

A repeat is evidence about where to look. If you are reviewing Mongodb server, the records below say which mistake has already been found more than once, which is the cheapest place a reviewer can start. If you are asking the vendor a question, a count under one weakness class is a better question than any single record is.

What this page cannot tell you is decided by what was joined. A product name and a weakness class settled membership, so those two values are the whole of what the page asserts. Records here may sit in the same line of code or in unrelated parts of the product, and we hold no value that separates those cases. A fixed version named in one record closes that record and says nothing about the others. And nothing here describes anyone's systems, because no value in this family connects a product name to an installation.

CVE-2026-13069, published 2026-07-22CVE-2026-13074, published 2026-07-22CVE-2026-13075, published 2026-07-22CVE-2026-13076, published 2026-07-22
All 4 were published on the same day, so this family is one announcement rather than a run.

The names the authorities used

One spelling, used by every authority that filed one of these records: mongodb server.

Family membership: held values. Joined on the product and weakness class the assigning authorities wrote, with no model involved.

What the records offer

All 4 records publish a fixed version.

What this page does not cover

This is a family of records that read alike. It is not a shared vulnerability, not an inventory, and not a statement that one fix closes the rest. Each record's own state, its own dates and its own receipts are on its own page.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Everything this vendor has, including records outside this family:

CVE-2026-13069Queryable Encryption FLE2 Find Payload Missing Input Validation Leading to Resource ExhaustionCWE-770: Allocation of Resources Without Limits…
CVE-2026-13074Awaitable Hello Command in Exhaust Mode Unthrottled Response Loop Leading to Denial of ServiceCWE-770: Allocation of Resources Without Limits…
CVE-2026-13075$rankFusion and $scoreFusion Unbounded Memory Allocation During Error Suggestion GenerationCWE-770: Allocation of Resources Without Limits…
CVE-2026-13076Aggregation Framework Memory Exhaustion Leading to Process TerminationCWE-770: Allocation of Resources Without Limits…

4 records, read from the index as it stood on 20 Sep 2026. Every row opens the record it names, and every value on that record opens its own receipt.

Everything on this page is free. Public data. Withholding it protects nothing.