Every change, newest first

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

55 changes · newest first · grouped by dayCSV JSON RSS

Showing changes seen on 2026-07-31. Every day

Counted changes changed on 2026-07-31, 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 31 Jul 2026· 55 changes
2026-07-31	Product added	CVE-2026-0631	tp-link systems inc. TPLink	not named as affected at publication, now names archer axe75 v1	Time to revision 179 days
2026-07-313 commits	Product added	Show all 3 CVE records in this change: Product added: 2 products named as affected from red hatHide the 3 CVE records in this change: Product added: 2 products named as affected from red hat6 rows, one per record and product	red hat	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support and 1 moreBranches and original-value intervals are stated on each row.	Time to revision 49 to 66 days
2026-07-31	same kind of change as the line above	CVE-2026-48864	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Time to revision 66 days
2026-07-31	same kind of change as the line above	CVE-2026-54228	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Time to revision 49 days
2026-07-31	same kind of change as the line above	CVE-2026-54228	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support	Time to revision 49 days
2026-07-31	same kind of change as the line above	CVE-2026-54229	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Time to revision 49 days
2026-07-31	same kind of change as the line above	CVE-2026-54229	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support	Time to revision 49 days
2026-07-31	same kind of change as the line above	CVE-2026-48864	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support	Time to revision 66 days
2026-07-312 commits	Product added	Show all 3 CVE records in this change: Product added: gimp named as affected from gnomeHide the 3 CVE records in this change: Product added: gimp named as affected from gnome	gnome redhat	not named as affected at publication, now names gimpBranches and original-value intervals are stated on each row.	Time to revision 4 days
2026-07-31	same kind of change as the line above	CVE-2026-66757	same vendor as the line above	same change as the line above	Time to revision 4 days
2026-07-31	same kind of change as the line above	CVE-2026-66758	same vendor as the line above	same change as the line above	Time to revision 4 days
2026-07-31	same kind of change as the line above	CVE-2026-66759	same vendor as the line above	same change as the line above	Time to revision 4 days
2026-07-31	Product added	CVE-2026-66420	ylianst VulnCheck	not named as affected at publication, now names meshcentral	Time to revision 1 days
2026-07-31	Product added	CVE-2026-16843Show all 4 products in this change: Product added: 4 products named as affected in CVE-2026-16843Hide the 4 products in this change: Product added: 4 products named as affected in CVE-2026-16843	hikvision	not named as affected at publication, now names ds-3wg105g-si and 3 more	Time to revision 0 days
2026-07-31	same kind of change as the line above	CVE-2026-16843	same vendor as the line above	not named as affected at publication, now names ds-3wg105g-si	Time to revision 0 days
2026-07-31	same kind of change as the line above	CVE-2026-16843	same vendor as the line above	not named as affected at publication, now names ds-3wg105gp-si	Time to revision 0 days
2026-07-31	same kind of change as the line above	CVE-2026-16843	same vendor as the line above	not named as affected at publication, now names ds-3wg210gp-si	Time to revision 0 days
2026-07-31	same kind of change as the line above	CVE-2026-16843	same vendor as the line above	not named as affected at publication, now names ds-3wg507g-si	Time to revision 0 days
2026-07-31	Product added	Show all 5 CVE records in this change: Product added: tbc named as affected from tbcHide the 5 CVE records in this change: Product added: tbc named as affected from tbc	tbc CSA	not named as affected at publication, now names tbc	Time to revision 0 days
2026-07-31	same kind of change as the line above	CVE-2026-43829	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-07-31	same kind of change as the line above	CVE-2026-43830	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-07-31	same kind of change as the line above	CVE-2026-43831	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-07-31	same kind of change as the line above	CVE-2026-43832	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-07-31	same kind of change as the line above	CVE-2026-43833	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-07-31	Record state changed	CVE-2026-6552	whole record GitLab	stated at publication PUBLISHED, now states REJECTED	Time to revision 50 days
2026-07-31	Record state changed	Show all 32 CVE records in this change: Record state changed: PUBLISHED → REJECTEDHide the 32 CVE records in this change: Record state changed: PUBLISHED → REJECTED	whole record mitre	stated at publication PUBLISHED, now states REJECTED	Time to revision 2 to 5 days
2026-07-31	same kind of change as the line above	CVE-2026-51235	same vendor as the line above	same change as the line above	Time to revision 5 days
2026-07-31	same kind of change as the line above	CVE-2026-51244	same vendor as the line above	same change as the line above	Time to revision 5 days
2026-07-31	same kind of change as the line above	CVE-2026-51251	same vendor as the line above	same change as the line above	Time to revision 4 days
2026-07-31	same kind of change as the line above	CVE-2026-51252	same vendor as the line above	same change as the line above	Time to revision 4 days
2026-07-31	same kind of change as the line above	CVE-2026-51254	same vendor as the line above	same change as the line above	Time to revision 4 days
2026-07-31	same kind of change as the line above	CVE-2026-51259	same vendor as the line above	same change as the line above	Time to revision 4 days
2026-07-31	same kind of change as the line above	CVE-2026-51260	same vendor as the line above	same change as the line above	Time to revision 4 days
2026-07-31	same kind of change as the line above	CVE-2026-51261	same vendor as the line above	same change as the line above	Time to revision 4 days
24 more rows in this change are not listed here. Open all 32 rows →
2026-07-31	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 CSA	stated at publication PUBLISHED, now states REJECTED	Time to revision 0 days
2026-07-31	same kind of change as the line above	CVE-2026-6889	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-07-31	same kind of change as the line above	CVE-2026-6890	same vendor as the line above	same change as the line above	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

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 →