Zephyrproject-rtos zephyr, out-of-bounds write: 12 records, one defect family
Zephyrproject-rtos zephyr has been reported 12 separate times for the same kind of mistake, CWE-787, between 2020-05-11 and 2026-06-09. 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 Zephyrproject-rtos zephyr and carries CWE-787, matched character for character. We show the join because a grouping you cannot check is a grouping you should not cite.
One record is an incident. 12 filings, between 2020-05-11 and 2026-06-09, all landing on the same weakness class in the same product, is a habit in what gets reported here, and a habit is something you can plan around. This is what we held on 2026-09-20.
A repeat is evidence about where to look. If you are reviewing Zephyrproject-rtos zephyr, 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.
The names the authorities used
One spelling, used by every authority that filed one of these records: zephyrproject-rtos zephyr.
Family membership: held values. Joined on the product and weakness class the assigning authorities wrote, with no model involved.
What the records offer
No record in this family publishes a fixed version in held sources.
The earliest was published 2020-05-11 and the latest 2026-06-09. That span is how long this product kept producing this weakness, not how long any one record took to fix.
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:
12 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.