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.

4 changes refused · newest first · grouped by dayCSVJSONRSS

SinceClear all
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.

Rows we checked and refused, counted nowhere from Nx, 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.
Tue 10 Jun 2025· 4 changes
2025-06-10Product addedCVE-2025-36852HeroDevsnot named as affected at publication, now names aws s3 remote cache plugin for nx and 3 morenot counted: No products named at publicationTime to revision 0 days
2025-06-10same kind of change as the line aboveCVE-2025-36852same vendor as the line abovenot named as affected at publication, now names aws s3 remote cache plugin for nxNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromTime to revision 0 days
2025-06-10same kind of change as the line aboveCVE-2025-36852same vendor as the line abovenot named as affected at publication, now names azure blob remote cache plugin for nxNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromTime to revision 0 days
2025-06-10same kind of change as the line aboveCVE-2025-36852same vendor as the line abovenot named as affected at publication, now names gcs remote cache plugin for nxNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromTime to revision 0 days
2025-06-10same kind of change as the line aboveCVE-2025-36852same vendor as the line abovenot named as affected at publication, now names shared file system cache plugin for nxNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromTime to revision 0 days

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 →