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.

9 changes behind one line · newest first

SinceClear the filter
ChangedSourceRows

One change, in full: Advisory severity changed: HIGH → CRITICAL. The same change in 9 advisories. Back to the ledger

Counted changes, newest first, one line per change to a GHSA advisory, 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.KindAdvisory, Which advisory was edited, by its GHSA id.Package, The package the advisory names, and the registry it comes from.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.
2023-08-03published 2023-07-28Advisory severity changedGHSA-859m-2pfx-fwhfCVE-2023-39022whole advisorycriticalstated at publication HIGH, now states CRITICALNo CVSS vector was stated in the first observed version.Days to revision 6
2023-08-03published 2023-07-28Advisory severity changedGHSA-fx3v-4w3w-wpwrCVE-2023-39021whole advisorycriticalstated at publication HIGH, now states CRITICALNo CVSS vector was stated in the first observed version.Days to revision 6
2023-08-03published 2023-07-28Advisory severity changedGHSA-2h26-qfxm-r3pqCVE-2023-37754whole advisorycriticalstated at publication HIGH, now states CRITICALNo CVSS vector was stated in the first observed version.Days to revision 6
2023-08-03published 2023-07-28Advisory severity changedGHSA-353m-jh2m-72v4CVE-2023-39020whole advisorycriticalstated at publication HIGH, now states CRITICALNo CVSS vector was stated in the first observed version.Days to revision 6
2023-08-03published 2023-07-28Advisory severity changedGHSA-99p5-qpqx-mhwcCVE-2023-39010whole advisorycriticalstated at publication HIGH, now states CRITICALNo CVSS vector was stated in the first observed version.Days to revision 6
2023-08-03published 2023-07-28Advisory severity changedGHSA-grvq-vjqr-x8vmCVE-2023-39015whole advisorycriticalstated at publication HIGH, now states CRITICALNo CVSS vector was stated in the first observed version.Days to revision 6
2023-08-03published 2023-07-28Advisory severity changedGHSA-p83q-99rc-vfmvCVE-2023-39013whole advisorycriticalstated at publication HIGH, now states CRITICALNo CVSS vector was stated in the first observed version.Days to revision 6
2023-08-03published 2023-07-28Advisory severity changedGHSA-wp6c-29r3-jqw9CVE-2023-38992whole advisorycriticalstated at publication HIGH, now states CRITICALNo CVSS vector was stated in the first observed version.Days to revision 6
2023-08-03published 2023-07-25Advisory severity changedGHSA-r5pv-7g89-cxmcCVE-2023-35088whole advisorycriticalstated at publication HIGH, now states CRITICALNo CVSS vector was stated in the first observed version.Days to revision 9

Counted in advisories, never added to the CVE and KEV figures. 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.

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 →