Every change, newest first

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

23 record changes · 7 advisory changes · newest first · grouped by dayCSV JSON RSS

SinceKindVendorSortClear all

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

Counted changes changed on 2026-07-21, newest first, one line per change to a CVE record or a GHSA advisory, 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 or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together.	Vendor or package, 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.
Tue 21 Jul 2026· 30 changes
2026-07-21	Added to CISA KEV	Show all 2 CVE records in this change: Added to CISA KEV: Core from WordPressHide the 2 CVE records in this change: Added to CISA KEV: Core from WordPress	WordPressCore	fix due 2026-08-04	Duration unknown
2026-07-21	same kind of change as the line above	CVE-2026-60137	same vendor as the line above	same change as the line above	Duration unknown
2026-07-21	same kind of change as the line above	CVE-2026-63030	same vendor as the line above	same change as the line above	Duration unknown
2026-07-21	Added to CISA KEV	CVE-2026-0770	LangflowLangflow CISA KEV	fix due 2026-07-24	Duration unknown
2026-07-21	Added to CISA KEV	CVE-2021-27137	DD-WRTDD-WRT CISA KEV	fix due 2026-07-24	Duration unknown
2026-07-21	Ransomware use confirmed	CVE-2026-0257	Palo Alto NetworksPAN-OS CISA KEV	stated at publication Unknown, now states Known	Time to revision 53 days
2026-07-21	Fix version moved	CVE-2026-64824	home-assistanthome assistant core VulnCheck	stated at publication 2026.6.0, now states 2026.7.0Release branch starts at 0.same day	Time to revision 0 days
2026-07-21	Product added	CVE-2026-47304Show all 3 products in this change: Product added: 3 products named as affected in CVE-2026-47304Hide the 3 products in this change: Product added: 3 products named as affected in CVE-2026-47304	microsoft	not named as affected at publication, now names microsoft visual studio 2017 version 15.9 (includes 15.0 - 15.8) and 2 more	Time to revision 7 days
2026-07-21	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names microsoft visual studio 2017 version 15.9 (includes 15.0 - 15.8)	Time to revision 7 days
2026-07-21	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names microsoft visual studio 2019 version 16.11 (includes 16.0 - 16.10)	Time to revision 7 days
2026-07-21	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names microsoft visual studio 2026 version 18.5	Time to revision 7 days
2026-07-21	Product added	Show all 4 CVE records in this change: Product added: red hat enterprise linux ai 3.5 for rhel 9 named as affected from red hatHide the 4 CVE records in this change: Product added: red hat enterprise linux ai 3.5 for rhel 9 named as affected from red hat	red hat	not named as affected at publication, now names red hat enterprise linux ai 3.5 for rhel 9	Time to revision 32 days
2026-07-21	same kind of change as the line above	CVE-2026-56208	same vendor as the line above	same change as the line above	Time to revision 32 days
2026-07-21	same kind of change as the line above	CVE-2026-56209	same vendor as the line above	same change as the line above	Time to revision 32 days
2026-07-21	same kind of change as the line above	CVE-2026-56210	same vendor as the line above	same change as the line above	Time to revision 32 days
2026-07-21	same kind of change as the line above	CVE-2026-56211	same vendor as the line above	same change as the line above	Time to revision 32 days
2026-07-21	Product added	CVE-2026-16118	xdg redhat	not named as affected at publication, now names xdgmime	Time to revision 4 days
2026-07-21	Product added	CVE-2025-57847	red hat	not named as affected at publication, now names red hat ansible automation platform 2.5	Time to revision 104 days
2026-07-21	Product added	CVE-2026-12701Show all 2 products in this change: Product added: 2 products named as affected in CVE-2026-12701Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2026-12701	red hat	not named as affected at publication, now names red hat ansible automation platform 2.6 and 1 more	Time to revision 1 days
2026-07-21	same kind of change as the line above	CVE-2026-12701	same vendor as the line above	not named as affected at publication, now names red hat ansible automation platform 2.6	Time to revision 1 days
2026-07-21	same kind of change as the line above	CVE-2026-12701	same vendor as the line above	not named as affected at publication, now names red hat ansible automation platform 2.7	Time to revision 1 days
2026-07-21	CVSS base score changed	CVE-2026-48356	whole record adobe	stated at publication 9.6, now states 9.3CVSS v3.1 · base scoreCriticalCritical	Time to revision 7 days
2026-07-21	Record state changed	Show all 4 CVE records in this change: Record state changed: PUBLISHED → REJECTEDHide the 4 CVE records in this change: Record state changed: PUBLISHED → REJECTED	whole record GitHub_M	stated at publication PUBLISHED, now states REJECTED	Time to revision 1 days
2026-07-21	same kind of change as the line above	CVE-2026-44507	same vendor as the line above	same change as the line above	Time to revision 1 days
2026-07-21	same kind of change as the line above	CVE-2026-44508	same vendor as the line above	same change as the line above	Time to revision 1 days
2026-07-21	same kind of change as the line above	CVE-2026-44509	same vendor as the line above	same change as the line above	Time to revision 1 days
2026-07-21	same kind of change as the line above	CVE-2026-44510	same vendor as the line above	same change as the line above	Time to revision 1 days
2026-07-21	Record state changed	CVE-2024-47220	whole record mitre	stated at publication PUBLISHED, now states REJECTED	Time to revision 668 days
2026-07-21published 2026-05-07	Package added to advisory	GHSA-g924-cjx7-2rjwCVE-2026-42597	go moderate	not named as affected when the advisory was published, now names github.com/gotenberg/gotenberg/v7	Time to revision 76 days
2026-07-21published 2026-04-14	Package added to advisory	GHSA-2hx3-vp6r-mg3fShow all 2 packages in this change: Package added to advisory: 2 packages named as affected in GHSA-2hx3-vp6r-mg3fHide the 2 packages in this change: Package added to advisory: 2 packages named as affected in GHSA-2hx3-vp6r-mg3f	nuget high	not named as affected when the advisory was published, now names microsoft.openapi.kiota and 1 more	Time to revision 98 days
2026-07-21published 2026-04-14	same kind of change as the line above	GHSA-2hx3-vp6r-mg3fCVE-2026-41134	same package registry as the line abovehigh	not named as affected when the advisory was published, now names microsoft.openapi.kiota	Time to revision 98 days
2026-07-21published 2026-04-14	same kind of change as the line above	GHSA-2hx3-vp6r-mg3fCVE-2026-41134	same package registry as the line abovehigh	not named as affected when the advisory was published, now names microsoft.openapi.kiota.builder	Time to revision 98 days
2026-07-21published 2025-08-26	Advisory severity changed	Show all 2 advisories in this change: Advisory severity changed: MODERATE → HIGHHide the 2 advisories in this change: Advisory severity changed: MODERATE → HIGH	whole advisoryhigh	stated at publication MODERATE, now states HIGHNo CVSS vector was stated in the first observed version.	Time to revision 329 to 329 days
2026-07-21published 2025-08-26	same kind of change as the line above	GHSA-xp4f-hrf8-rxw7CVE-2025-71344	same package and registry as the line abovehigh	same change as the line above	Time to revision 329 days
2026-07-21published 2025-08-26	same kind of change as the line above	GHSA-3vg9-h568-4w9mCVE-2025-71354	same package and registry as the line abovehigh	same change as the line above	Time to revision 329 days
2026-07-21published 2026-06-23	Advisory severity changed	GHSA-vcm5-gvmp-78mpCVE-2026-52807	whole advisorymoderate	stated at publication HIGH, now states MODERATENo CVSS vector was stated in the first observed version.	Time to revision 28 days
2026-07-21published 2026-06-22	Advisory severity changed	GHSA-c4v7-xg93-qf8gCVE-2026-47267	whole advisoryhigh	stated at publication MODERATE, now states HIGHNo CVSS vector was stated in the first observed version.	Time to revision 29 days

Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. 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 →