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

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 changes
2026-09-04	Product added	Show all 3 CVE records in this change: Product added: gfi clearview named as affected from gfi softwareHide the 3 CVE records in this change: Product added: gfi clearview named as affected from gfi software	gfi software VulnCheck	not named as affected at publication, now names gfi clearview	Time to revision 0 days
2026-09-04	same kind of change as the line above	CVE-2026-74235	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-09-04	same kind of change as the line above	CVE-2026-74236	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-09-04	same kind of change as the line above	CVE-2026-74237	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-09-04	Record state changed	CVE-2026-18745	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Time to revision 0 days
Thu 3 Sep 2026· 1 change
2026-09-03	Record state changed	CVE-2026-76848	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Time to revision 10 days
Wed 2 Sep 2026· 1 change
2026-09-02	Record state changed	CVE-2026-39909	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Time to revision 12 days
Tue 1 Sep 2026· 5 changes
2026-09-01	Record state changed	Show all 5 CVE records in this change: Record state changed: PUBLISHED → REJECTEDHide the 5 CVE records in this change: Record state changed: PUBLISHED → REJECTED	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Time to revision 7 days
2026-09-01	same kind of change as the line above	CVE-2024-58377	same vendor as the line above	same change as the line above	Time to revision 7 days
2026-09-01	same kind of change as the line above	CVE-2024-58378	same vendor as the line above	same change as the line above	Time to revision 7 days
2026-09-01	same kind of change as the line above	CVE-2025-71346	same vendor as the line above	same change as the line above	Time to revision 7 days
2026-09-01	same kind of change as the line above	CVE-2025-71406	same vendor as the line above	same change as the line above	Time to revision 7 days
2026-09-01	same kind of change as the line above	CVE-2025-71407	same vendor as the line above	same change as the line above	Time to revision 7 days
Mon 31 Aug 2026· 2 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	Time to revision 12 days
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	Time to revision 16 days
Fri 28 Aug 2026· 3 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	Time to revision 11 days
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	Time to revision 15 days
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	Time to revision 3 days
Wed 26 Aug 2026· 2 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	Time to revision 15 days
2026-08-26	Record state changed	CVE-2026-74234	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Time to revision 9 days
Mon 24 Aug 2026· 13 changes
2026-08-24	CVSS base score changed	Show all 13 CVE records in this change: CVSS base score changed: 9.8 → 8.8Hide the 13 CVE records in this change: CVSS base score changed: 9.8 → 8.8	whole record VulnCheck	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 10 to 190 days
2026-08-24	same kind of change as the line above	CVE-2026-26369	same vendor as the line above	same change as the line above	Time to revision 190 days
2026-08-24	same kind of change as the line above	CVE-2026-34100	same vendor as the line above	same change as the line above	Time to revision 54 days
2026-08-24	same kind of change as the line above	CVE-2026-34101	same vendor as the line above	same change as the line above	Time to revision 54 days
2026-08-24	same kind of change as the line above	CVE-2026-34102	same vendor as the line above	same change as the line above	Time to revision 54 days
2026-08-24	same kind of change as the line above	CVE-2026-34103	same vendor as the line above	same change as the line above	Time to revision 54 days
2026-08-24	same kind of change as the line above	CVE-2026-34104	same vendor as the line above	same change as the line above	Time to revision 54 days
2026-08-24	same kind of change as the line above	CVE-2026-34105	same vendor as the line above	same change as the line above	Time to revision 54 days
2026-08-24	same kind of change as the line above	CVE-2026-39910	same vendor as the line above	same change as the line above	Time to revision 77 days
5 more rows in this change are not listed here. Open all 13 rows →
Wed 19 Aug 2026· 1 change
2026-08-19	Record state changed	CVE-2026-73682	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Time to revision 5 days
Tue 18 Aug 2026· 1 change
2026-08-18	Record state changed	CVE-2026-73692	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Time to revision 0 days
Mon 17 Aug 2026· 1 change
2026-08-17	Record state changed	CVE-2026-73327	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Time to revision 5 days
Fri 14 Aug 2026· 1 change
2026-08-14	Product added	CVE-2026-73039	streamaserver VulnCheck	not named as affected at publication, now names streama	Time to revision 1 days
Thu 13 Aug 2026· 1 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.	Time to revision 7 days
Wed 12 Aug 2026· 2 changes
2026-08-12	Record state changed	Show all 2 CVE records in this change: Record state changed: PUBLISHED → REJECTEDHide the 2 CVE records in this change: Record state changed: PUBLISHED → REJECTED	whole record VulnCheck	stated at publication PUBLISHED, now states REJECTED	Time to revision 1 days
2026-08-12	same kind of change as the line above	CVE-2026-72745	same vendor as the line above	same change as the line above	Time to revision 1 days
2026-08-12	same kind of change as the line above	CVE-2026-72746	same vendor as the line above	same change as the line above	Time to revision 1 days
Tue 11 Aug 2026· 2 changes
2026-08-11	Fix version moved	Show all 2 CVE records in this change: Fix version moved: 2.4.4 → 2.4.5 from usmannasirHide the 2 CVE records in this change: Fix version moved: 2.4.4 → 2.4.5 from usmannasir	usmannasircyberpanel VulnCheck	stated at publication 2.4.4, now states 2.4.5Release branch starts at 0.	Time to revision 109 days
2026-08-11	same kind of change as the line above	CVE-2026-41472	same vendor as the line above	same change as the line aboveRelease branch starts at 0.	Time to revision 109 days
2026-08-11	same kind of change as the line above	CVE-2026-41473	same vendor as the line above	same change as the line aboveRelease branch starts at 0.	Time to revision 109 days
Mon 10 Aug 2026· 1 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	Time 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.

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 →