Skip to content

Every change, newest first

Compare earlier and later source statements, with the dates and evidence behind each measured change.

16 advisory changes · newest first · grouped by day

SinceClear all
ChangedSourceRows

Showing changes seen on 2026-02-03. Every day

Counted changes changed on 2026-02-03, 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.
Tue 3 Feb 2026· 16 changes
2026-02-03published 2026-02-02Advisory fix version movedGHSA-gc24-px2r-5qmfCVE-2026-25505
pypibambuddy
critical
stated at publication 0.1.6.2, now states 0.1.7Time to revision 1 days
2026-02-03published 2021-03-11Advisory severity changedGHSA-gmrf-99gw-vvwjCVE-2021-46876whole advisorymoderatestated at publication HIGH, now states MODERATENo CVSS vector was stated in the first observed version.Duration unknown
2026-02-03published 2019-06-03 to 2026-01-26Advisory withdrawnwhole advisory4 bandswithdrawn 2026-02-03Time to revision 8 to 2,437 days
2026-02-03published 2022-02-11same kind of change as the line aboveGHSA-76wf-9vgp-pj7wsame package and registry as the line abovemoderatewithdrawn 2026-02-03Time to revision 1,453 days
2026-02-03published 2022-06-17same kind of change as the line aboveGHSA-6692-8qqf-79jcsame package and registry as the line abovehighwithdrawn 2026-02-03Time to revision 1,328 days
2026-02-03published 2019-06-03same kind of change as the line aboveGHSA-3fc5-9x9m-vqc4same package and registry as the line abovecriticalwithdrawn 2026-02-03Time to revision 2,437 days
2026-02-03published 2024-05-30same kind of change as the line aboveGHSA-75mx-chcf-2q32same package and registry as the line abovemoderatewithdrawn 2026-02-03Time to revision 614 days
2026-02-03published 2023-12-20same kind of change as the line aboveGHSA-mhpq-9638-x6pwsame package and registry as the line abovemoderatewithdrawn 2026-02-03Time to revision 776 days
2026-02-03published 2020-09-03same kind of change as the line aboveGHSA-4xf9-pgvv-xx67same package and registry as the line abovemoderatewithdrawn 2026-02-03Time to revision 1,979 days
2026-02-03published 2019-06-06same kind of change as the line aboveGHSA-g95f-p29q-9xw4same package and registry as the line abovelowwithdrawn 2026-02-03Time to revision 2,434 days
2026-02-03published 2026-01-26same kind of change as the line aboveGHSA-p5wg-g6qr-c7cgCVE-2025-50537same package and registry as the line abovemoderatewithdrawn 2026-02-03Time to revision 8 days
6 more rows in this change are not listed here. Open all 14 rows

Counted in advisories, never added to the CVE and KEV figures. Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

What this page cannot see

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 →

Paste your closed CVE tickets and see which of these changes hit them →