Product added
Showing changes seen on 2026-03-13. Every day
| Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin. | Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on. | Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry. | What changed | Days to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong. |
|---|---|---|---|---|
| Fri 13 Mar 2026· 23 record changes | ||||
| 2026-03-133 commits | 21 rows, one per record and product | not named as affected at publication, now names windows 10 version 1607 and 10 moreBranches and original-value intervals are stated on each row. | Days to revision 3 to 31 | |
| 2026-03-13 | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 10 version 1607 | Days to revision 3 |
| 2026-03-13 | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 10 version 1809 | Days to revision 3 |
| 2026-03-13 | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 10 version 21h2 | Days to revision 3 |
| 2026-03-13 | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 10 version 22h2 | Days to revision 3 |
| 2026-03-13 | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 11 version 22h3 | Days to revision 3 |
| 2026-03-13 | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 11 version 23h2 | Days to revision 3 |
| 2026-03-13 | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 11 version 24h2 | Days to revision 3 |
| 2026-03-13 | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 11 version 25h2 | Days to revision 3 |
| 13 more rows in this change are not listed here. Open all 21 rows → | ||||
| 2026-03-13 | TPLink | not named as affected at publication, now names tapo d235 v1 | Days to revision 31 | |
| 2026-03-13 | CVE-2026-0651 | same vendor as the line above | same change as the line above | Days to revision 31 |
| 2026-03-13 | CVE-2026-0653 | same vendor as the line above | same change as the line above | Days to revision 31 |
This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
Data sources and quality
Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
The units, the refusals, the cut-offs and every source, in full →