Microsoft windows 10 version 1507, out-of-bounds write: 9 records, one defect family
Microsoft windows 10 version 1507 has been reported 9 separate times for the same kind of mistake, CWE-787, between 2020-05-21 and 2022-11-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 Microsoft windows 10 version 1507 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. 9 filings, between 2020-05-21 and 2022-11-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 Microsoft windows 10 version 1507, 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: microsoft windows 10 version 1507.
Family membership: held values. Joined on the product and weakness class the assigning authorities wrote, with no model involved.
What the records offer
6 of 9 records publish a fixed version. For the other 3, held sources name none.
5 records are listed by CISA with a required action, which carries a federal remediation deadline on its own page.
The earliest was published 2020-05-21 and the latest 2022-11-09. That span is how long this product kept producing this weakness, not how long any one record took to fix.
What this family was researched, not held
Out of bounds writes kept landing on the first Windows 10 build
This grouping sits on version 1507, the original Windows 10 release, and the fault that keeps returning is a write past the end of a buffer in a component that handles untrusted content. It kept recurring because the affected components are the ones that parse things for a living: a kernel mode graphics driver, media handling, scripting engines, and the print spooler. Four of these records were being exploited before or as their fix shipped. Microsoft reported the July 2021 scripting engine record, CVE-2021-34448, as exploited in the wild as a zero day, and CISA added the November 2022 print spooler, key isolation service and scripting languages records to its exploited catalog on 8 November 2022, the same day the updates appeared, with the print spooler record flagged as used in ransomware campaigns. The build outlived its consumer lifetime because the 2015 long term servicing edition ran on a fixed lifecycle from July 2015, with extended support listed as ending on 15 October 2025.
This build survives on fixed function machines that were bought to stay unchanged, and a memory safety defect in printing, scripting or graphics reaches them exactly as it reaches a desktop. The patch window on this line has repeatedly been zero, since four of these records were already under exploitation when the fix arrived. Microsoft's extended support for the 2015 long term servicing edition is listed as ended, so anything still on it is past its fixed lifecycle.
This note does not establish that these records share a vulnerability, a component, a fix or an estate. They were grouped because they read alike, and installing the update for one of them does not address any other. It also does not say which build you are running.
Written from learn.microsoft.com, tenable.com, cisa.gov, tenable.com. Stated at medium confidence. Nothing in this box is a value the index holds, and none of it opens a receipt.
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:
9 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.