Every change, newest first

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

41 changes · newest first · grouped by dayCSV JSON RSS

SinceKindVendorSortClear all

PublisherPublishedChangedSourceRows

Counted changes 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.
Fri 4 Sep 2026· 4 record changes
2026-09-04	Product added	CVE-2026-74235	gfi software VulnCheck	not named as affected at publication, now names gfi clearview	Days to revision 0
2026-09-04	Product added	CVE-2026-74236	gfi software VulnCheck	not named as affected at publication, now names gfi clearview	Days to revision 0
2026-09-04	Product added	CVE-2026-74237	gfi software VulnCheck	not named as affected at publication, now names gfi clearview	Days to revision 0
2026-09-04	Record state changed	CVE-2026-18745	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 0
Thu 3 Sep 2026· 1 record change
2026-09-03	Record state changed	CVE-2026-76848	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 10
Wed 2 Sep 2026· 1 record change
2026-09-02	Record state changed	CVE-2026-39909	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 12
Tue 1 Sep 2026· 5 record changes
2026-09-01	Record state changed	CVE-2024-58377	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 7
2026-09-01	Record state changed	CVE-2024-58378	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 7
2026-09-01	Record state changed	CVE-2025-71346	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 7
2026-09-01	Record state changed	CVE-2025-71406	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 7
2026-09-01	Record state changed	CVE-2025-71407	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 7
Mon 31 Aug 2026· 2 record changes
2026-08-31	Product added	CVE-2026-71960	shenzhen cudy technology co., ltd. VulnCheck	not named as affected at publication, now names p5 v1.1	Days to revision 12
2026-08-31	CVSS base score changed	CVE-2026-73055	whole record VulnCheck	stated at publication 9.3, now states 6.3CVSS v4.0 · base scoreCriticalMedium	Days to revision 16
Fri 28 Aug 2026· 3 record changes
2026-08-28	CVSS base score changed	CVE-2026-74887	whole record VulnCheck	stated at publication 9.3, now states 6.3CVSS v4.0 · base scoreCriticalMedium	Days to revision 11
2026-08-28	CVSS base score changed	CVE-2026-73626	whole record VulnCheck	stated at publication 0.0, now states 7.7CVSS v4.0 · base scoreNoneHigh	Days to revision 15
2026-08-28	CVSS base score changed	CVE-2026-80200	whole record VulnCheck	stated at publication 0.0, now states 5.3CVSS v4.0 · base scoreNoneMedium	Days to revision 3
Wed 26 Aug 2026· 2 record changes
2026-08-26	CVSS base score changed	CVE-2026-5917	whole record VulnCheck	stated at publication 9.6, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 15
2026-08-26	Record state changed	CVE-2026-74234	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 9
Mon 24 Aug 2026· 13 record changes
2026-08-24	CVSS base score changed	CVE-2026-26369	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 190
2026-08-24	CVSS base score changed	CVE-2026-34100	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 54
2026-08-24	CVSS base score changed	CVE-2026-34101	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 54
2026-08-24	CVSS base score changed	CVE-2026-34102	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 54
2026-08-24	CVSS base score changed	CVE-2026-34103	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 54
2026-08-24	CVSS base score changed	CVE-2026-34104	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 54
2026-08-24	CVSS base score changed	CVE-2026-34105	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 54
2026-08-24	CVSS base score changed	CVE-2026-39910	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 77
2026-08-24	CVSS base score changed	CVE-2026-72822	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 10
2026-08-24	CVSS base score changed	CVE-2026-72824	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 10
2026-08-24	CVSS base score changed	CVE-2026-72826	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 10
2026-08-24	CVSS base score changed	CVE-2026-72829	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 10
2026-08-24	CVSS base score changed	CVE-2026-72830	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 10
Wed 19 Aug 2026· 1 record change
2026-08-19	Record state changed	CVE-2026-73682	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 5
Tue 18 Aug 2026· 1 record change
2026-08-18	Record state changed	CVE-2026-73692	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 0
Mon 17 Aug 2026· 1 record change
2026-08-17	Record state changed	CVE-2026-73327	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 5
Fri 14 Aug 2026· 1 record change
2026-08-14	Product added	CVE-2026-73039	streamaserver VulnCheck	not named as affected at publication, now names streama	Days to revision 1
Thu 13 Aug 2026· 1 record change
2026-08-13	Affected range extended	CVE-2026-70556	hubzillahubzilla VulnCheck	stated at publication 11.2.1, now states 11.4Release branch starts at 0.	Days to revision 7
Wed 12 Aug 2026· 2 record changes
2026-08-12	Record state changed	CVE-2026-72745	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 1
2026-08-12	Record state changed	CVE-2026-72746	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Days to revision 1
Tue 11 Aug 2026· 2 record changes
2026-08-11	Fix version moved	CVE-2026-41472	usmannasircyberpanel VulnCheck	stated at publication 2.4.4, now states 2.4.5Release branch starts at 0.	Days to revision 109
2026-08-11	Fix version moved	CVE-2026-41473	usmannasircyberpanel VulnCheck	stated at publication 2.4.4, now states 2.4.5Release branch starts at 0.	Days to revision 109
Mon 10 Aug 2026· 1 record change
2026-08-10	CVSS base score changed	CVE-2026-66738	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Days to revision 0

Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none.

3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 03:47 UTC · scroll for earlierfewermore

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

Data sources and quality

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 →

Check my CVEs against these changes →