Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

17 changes refused · newest first · grouped by dayCSV JSON RSS

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 published by VulnCheck, from the last 30 days, 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.	Kind	Record, 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 changed	Days 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.
Sat 5 Sep 2026· 3 changes
2026-09-05	Product added	CVE-2026-85599	getgrav VulnCheck	not named as affected at publication, now names grav-plugin-shortcode-coreNot counted: Product relabelled. probable relabelling of getgrav/grav, not a newly affected product	Time to revision 1 days
2026-09-05	Product added	CVE-2026-85600	getgrav VulnCheck	not named as affected at publication, now names grav-plugin-admin2Not counted: Product relabelled. probable relabelling of getgrav/grav, not a newly affected product	Time to revision 1 days
2026-09-05	Product added	CVE-2026-85602	getgrav VulnCheck	not named as affected at publication, now names grav-plugin-formNot counted: Product relabelled. probable relabelling of getgrav/grav, not a newly affected product	Time to revision 1 days
Wed 2 Sep 2026· 1 change
2026-09-02	Affected range extended	CVE-2026-82641	keploykeploy VulnCheck	stated at publication 3.6.25, now states 3.6.26Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 3.6.25 still holds	Duration unknown
Tue 1 Sep 2026· 8 changes
2026-09-01	Product added	Show all 8 CVE records in this change: Product added: planet gs-4210-16p2s v3 named as affected from planet technology corp.Hide the 8 CVE records in this change: Product added: planet gs-4210-16p2s v3 named as affected from planet technology corp.	planet technology corp. VulnCheck	not named as affected at publication, now names planet gs-4210-16p2s v3not counted: Product relabelled	Time to revision 4 days
2026-09-01	same kind of change as the line above	CVE-2026-75121	same vendor as the line above	same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product	Time to revision 4 days
2026-09-01	same kind of change as the line above	CVE-2026-75122	same vendor as the line above	same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product	Time to revision 4 days
2026-09-01	same kind of change as the line above	CVE-2026-75123	same vendor as the line above	same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product	Time to revision 4 days
2026-09-01	same kind of change as the line above	CVE-2026-75124	same vendor as the line above	same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product	Time to revision 4 days
2026-09-01	same kind of change as the line above	CVE-2026-75125	same vendor as the line above	same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product	Time to revision 4 days
2026-09-01	same kind of change as the line above	CVE-2026-75126	same vendor as the line above	same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product	Time to revision 4 days
2026-09-01	same kind of change as the line above	CVE-2026-77217	same vendor as the line above	same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product	Time to revision 4 days
2026-09-01	same kind of change as the line above	CVE-2026-77218	same vendor as the line above	same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product	Time to revision 4 days
Sat 29 Aug 2026· 1 change
2026-08-29	Product added	CVE-2026-72699	getgrav VulnCheck	not named as affected at publication, now names grav-plugin-loginNot counted: Product relabelled. probable relabelling of getgrav/grav, not a newly affected product	Time to revision 4 days
Wed 26 Aug 2026· 1 change
2026-08-26	Affected range extended	CVE-2026-5917	libgit2libgit2 VulnCheck	stated at publication 1.9.0, now states 1.9.7Release branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched	Duration unknown
Tue 25 Aug 2026· 1 change
2026-08-25	Affected range extended	CVE-2026-73325	fujitsu researchonecompression VulnCheck	stated at publication 1.2.0, now states 1.2.1Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Time to revision 12 days
Mon 24 Aug 2026· 1 change
2026-08-24	CVSS base score changed	CVE-2026-67340	whole record VulnCheck	stated at publication 9.8, now states 8.6Assessments not comparable · base scoreCriticalHighNot 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 comparable	Time to revision 23 days
Fri 21 Aug 2026· 1 change
2026-08-21	Fix version moved	CVE-2026-63722	icecodericecoder VulnCheck	stated at publication 8.1, now states 8.1Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator	Time to revision 2 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.

4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

Every kind of change

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub advisory

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 →