Skip to content

Product added

What a record said when it was published, what it says now, and the commit that changed it.

20 changes behind one line · newest firstCSVJSONRSS

SinceClear the filter

One change, in full: Product added: 6 products named as affected from microsoft. Products named as affected in 9 CVE records, across 6 products: 20 rows in all, one per record and product. Drawn here as 3 lines, one per product. Back to the ledger

Counted changes of "Product added", newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
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 changedDays 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.
2025-05-152 commitsnot named as affected at publication, now names microsoft office ltsc for mac 2021Branches and original-value intervals are stated on each row.Days to revision 2
2025-05-15CVE-2025-29977same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-29979same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-30375same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-30379same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-30381same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-30383same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-30393same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-30376same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-152 commitsnot named as affected at publication, now names microsoft office ltsc for mac 2024Branches and original-value intervals are stated on each row.Days to revision 2
2025-05-15CVE-2025-29977same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-29979same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-30375same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-30379same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-30381same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-30383same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-30393same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-30376same vendor as the line abovesame change as the line aboveDays to revision 2
2025-05-15CVE-2025-32709not named as affected at publication, now names windows server 2008 r2 service pack 1 and 3 moreDays to revision 2
2025-05-15CVE-2025-32709same vendor as the line abovenot named as affected at publication, now names windows server 2008 r2 service pack 1Days to revision 2
2025-05-15CVE-2025-32709same vendor as the line abovenot named as affected at publication, now names windows server 2008 r2 service pack 1 (server core installation)Days to revision 2
2025-05-15CVE-2025-32709same vendor as the line abovenot named as affected at publication, now names windows server 2008 service pack 2Days to revision 2
2025-05-15CVE-2025-32709same vendor as the line abovenot named as affected at publication, now names windows server 2008 service pack 2 (server core installation)Days to revision 2

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 →

Check my CVEs against these changes →