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.

14 refused changes behind one line · newest first

SinceClear the filter
ChangedSourceRows

These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.

One change, in full: Package added to advisory: 3 packages named as affected in go. The same change in 14 advisories, across 3 packages. Drawn here as 3 lines, one per package. Back to the ledger

Rows we checked and refused, counted nowhere, 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.
2026-03-27published 2026-03-24 to 2026-03-25Package added to advisory2 bandsnot named as affected when the advisory was published, now names github.com/nats-io/nats-serverTime to revision 2 to 3 days
2026-03-27published 2026-03-25same kind of change as the line aboveGHSA-pq2q-rcw4-3hr6CVE-2026-27889same package registry as the line abovehighsame change as the line aboveTime to revision 2 days
2026-03-27published 2026-03-24same kind of change as the line aboveGHSA-3f24-pcvm-5jqcCVE-2026-33248same package registry as the line abovemoderatesame change as the line aboveTime to revision 3 days
2026-03-27published 2026-03-24same kind of change as the line aboveGHSA-55h8-8g96-x4hjCVE-2026-33246same package registry as the line abovemoderatesame change as the line aboveTime to revision 3 days
2026-03-27published 2026-03-24same kind of change as the line aboveGHSA-pwx7-fx9r-hr4hCVE-2026-33223same package registry as the line abovemoderatesame change as the line aboveTime to revision 3 days
2026-03-27published 2026-03-24same kind of change as the line aboveGHSA-9983-vrx2-fg9cCVE-2026-33222same package registry as the line abovemoderatesame change as the line aboveTime to revision 3 days
2026-03-27published 2026-03-24same kind of change as the line aboveGHSA-8r68-gvr4-jh7jCVE-2026-33219same package registry as the line abovemoderatesame change as the line aboveTime to revision 3 days
2026-03-27published 2026-03-24same kind of change as the line aboveGHSA-vprv-35vv-q339CVE-2026-33218same package registry as the line abovehighsame change as the line aboveTime to revision 3 days
2026-03-27published 2026-03-24same kind of change as the line aboveGHSA-jxxm-27vp-c3m5CVE-2026-33217same package registry as the line abovehighsame change as the line aboveTime to revision 3 days
2 more rows in this change are not listed here. Open all 10 rows
2026-03-27published 2026-03-24Package added to advisorymoderatenot named as affected when the advisory was published, now names github.com/pinchtab/pinchtabTime to revision 3 days
2026-03-27published 2026-03-24same kind of change as the line aboveGHSA-p8mm-644p-phmhCVE-2026-33623same package registry as the line abovemoderatesame change as the line aboveTime to revision 3 days
2026-03-27published 2026-03-24same kind of change as the line aboveGHSA-w5pc-m664-r62vCVE-2026-33622same package registry as the line abovemoderatesame change as the line aboveTime to revision 3 days
2026-03-27published 2026-03-13Package added to advisory2 bandsnot named as affected when the advisory was published, now names github.com/centrifugal/centrifugoTime to revision 14 to 14 days
2026-03-27published 2026-03-13same kind of change as the line aboveGHSA-q926-c743-49qjsame package registry as the line abovelowsame change as the line aboveTime to revision 14 days
2026-03-27published 2026-03-13same kind of change as the line aboveGHSA-j77h-rr39-c552CVE-2026-32301same package registry as the line abovecriticalsame change as the line aboveTime to revision 14 days

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.

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 →