Skip to content

Every change, newest first

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

100 changes behind one line · newest firstCSVJSONRSS

SinceClear all
ChangedSourceRows

One change, in full: Product added: 33 products named as affected from poly. Products named as affected in 4 CVE records, across 33 products: 100 rows in all, one per record and product. Drawn here as 4 lines, one per product. Back to the ledger

Counted changes from poly, published by VulDB, 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.KindRecord, 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.
2024-01-09Product addedCVE-2023-4462VulDBnot named as affected at publication, now names ccx 350 and 32 moreDays to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4462same vendor as the line abovenot named as affected at publication, now names ccx 350Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4462same vendor as the line abovenot named as affected at publication, now names ccx 500Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4462same vendor as the line abovenot named as affected at publication, now names ccx 505Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4462same vendor as the line abovenot named as affected at publication, now names ccx 700Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4462same vendor as the line abovenot named as affected at publication, now names edge e100Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4462same vendor as the line abovenot named as affected at publication, now names edge e220Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4462same vendor as the line abovenot named as affected at publication, now names edge e300Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4462same vendor as the line abovenot named as affected at publication, now names edge e320Days to revision 11
25 more rows in this change are not listed here. Open all 33 rows
2024-01-09Product addedCVE-2023-4464VulDBnot named as affected at publication, now names ccx 350 and 32 moreDays to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4464same vendor as the line abovenot named as affected at publication, now names ccx 350Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4464same vendor as the line abovenot named as affected at publication, now names ccx 500Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4464same vendor as the line abovenot named as affected at publication, now names ccx 505Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4464same vendor as the line abovenot named as affected at publication, now names ccx 700Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4464same vendor as the line abovenot named as affected at publication, now names edge e100Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4464same vendor as the line abovenot named as affected at publication, now names edge e220Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4464same vendor as the line abovenot named as affected at publication, now names edge e300Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4464same vendor as the line abovenot named as affected at publication, now names edge e320Days to revision 11
25 more rows in this change are not listed here. Open all 33 rows
2024-01-09Product addedCVE-2023-4465VulDBnot named as affected at publication, now names ccx 350 and 32 moreDays to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4465same vendor as the line abovenot named as affected at publication, now names ccx 350Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4465same vendor as the line abovenot named as affected at publication, now names ccx 500Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4465same vendor as the line abovenot named as affected at publication, now names ccx 505Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4465same vendor as the line abovenot named as affected at publication, now names ccx 700Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4465same vendor as the line abovenot named as affected at publication, now names edge e100Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4465same vendor as the line abovenot named as affected at publication, now names edge e220Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4465same vendor as the line abovenot named as affected at publication, now names edge e300Days to revision 11
2024-01-09same kind of change as the line aboveCVE-2023-4465same vendor as the line abovenot named as affected at publication, now names edge e320Days to revision 11
25 more rows in this change are not listed here. Open all 33 rows
2024-01-09Product addedCVE-2023-4468VulDBnot named as affected at publication, now names trio 8500Days to revision 11

Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. 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 →