Skip to content

Every change, newest first

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

3 record edits refused · 14 advisory changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

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

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.

Rows we checked and refused, counted nowhere changed on 2026-03-27, newest first, one line per change to a CVE record or 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.KindRecord or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together.Vendor or package, 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.
Fri 27 Mar 2026· 17 changes
2026-03-27CVSS base score changedCVE-2025-53521
whole record
f5
stated at publication 8.7, now states 9.8Assessments not comparable · base scoreHighCriticalNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparableTime to revision 163 days
2026-03-27CVSS base score changedCVE-2026-32857
whole record
VulnCheck
stated at publication 7.8, now states 8.6Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedTime to revision 1 days
2026-03-27CVSS base score changedCVE-2026-32859
whole record
VulnCheck
stated at publication 5.1, now states 5.4Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedTime to revision 0 days
2026-03-27published 2026-03-13 to 2026-03-25Package added to advisory4 bandsnot named as affected when the advisory was published, now names github.com/nats-io/nats-server and 2 moreTime to revision 2 to 14 days
2026-03-27published 2026-03-25same kind of change as the line aboveGHSA-pq2q-rcw4-3hr6CVE-2026-27889same package registry as the line abovehighnot named as affected when the advisory was published, now names github.com/nats-io/nats-serverTime 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 abovemoderatenot named as affected when the advisory was published, now names github.com/nats-io/nats-serverTime 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 abovemoderatenot named as affected when the advisory was published, now names github.com/nats-io/nats-serverTime 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 abovemoderatenot named as affected when the advisory was published, now names github.com/nats-io/nats-serverTime 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 abovemoderatenot named as affected when the advisory was published, now names github.com/nats-io/nats-serverTime 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 abovemoderatenot named as affected when the advisory was published, now names github.com/nats-io/nats-serverTime 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 abovehighnot named as affected when the advisory was published, now names github.com/nats-io/nats-serverTime 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 abovehighnot named as affected when the advisory was published, now names github.com/nats-io/nats-serverTime to revision 3 days
6 more rows in this change are not listed here. Open all 14 rows

Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. 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 →