Every change, newest first

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

20 changes · newest first · grouped by dayCSV JSON RSS

PublisherPublishedChangedSourceRows

Counted changes published by vmware, 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.
Thu 27 Aug 2026· 2 changes
2026-08-27	Product added	CVE-2026-59323	spring vmware	not named as affected at publication, now names micrometer tracing	Time to revision 6 days
2026-08-27	CVSS base score changed	CVE-2026-59354	whole record vmware	stated at publication 6.1, now states 9.6CVSS v3.1 · base scoreMediumCritical	Time to revision 0 days
Tue 23 Jun 2026· 1 change
2026-06-23	Fix version moved	CVE-2026-41715	springreactor netty vmware	stated at publication 1.3.6, now states 1.3.15.1Release branch starts at 1.3.0.	Time to revision 15 days
Wed 29 Apr 2026· 2 changes
2026-04-29	CVSS base score changed	CVE-2026-22740	whole record vmware	stated at publication 0.0, now states 6.5CVSS v3.1 · base scoreNoneMedium	Time to revision 0 days
2026-04-29	CVSS base score changed	CVE-2026-22741	whole record vmware	stated at publication 0.0, now states 3.1CVSS v3.1 · base scoreNoneLow	Time to revision 0 days
Tue 28 Apr 2026· 1 change
2026-04-28	CVSS base score changed	CVE-2026-40967	whole record vmware	stated at publication 8.2, now states 8.6CVSS v3.1 · base scoreHighHigh	Time to revision 0 days
Tue 14 Apr 2026· 1 change
2026-04-14	Product added	CVE-2026-22719	vmware	not named as affected at publication, now names vmware cloud foundation operations	Time to revision 48 days
Fri 27 Feb 2026· 1 change
2026-02-27	CVSS base score changed	CVE-2026-22716	whole record vmware	stated at publication 2.7, now states 5.0CVSS v3.1 · base scoreLowMedium	Time to revision 0 days
Mon 29 Sep 2025· 5 changes
2025-09-29	Product added	CVE-2025-41250	vmware	not named as affected at publication, now names vsphere foundation	Time to revision 0 days
2025-09-29	Product added	CVE-2025-41244Show all 4 products in this change: Product added: 4 products named as affected in CVE-2025-41244Hide the 4 products in this change: Product added: 4 products named as affected in CVE-2025-41244	vmware	not named as affected at publication, now names vmware aria operations and 3 more	Time to revision 0 days
2025-09-29	same kind of change as the line above	CVE-2025-41244	same vendor as the line above	not named as affected at publication, now names vmware aria operations	Time to revision 0 days
2025-09-29	same kind of change as the line above	CVE-2025-41244	same vendor as the line above	not named as affected at publication, now names vmware cloud foundation	Time to revision 0 days
2025-09-29	same kind of change as the line above	CVE-2025-41244	same vendor as the line above	not named as affected at publication, now names vmware telco cloud infrastructure	Time to revision 0 days
2025-09-29	same kind of change as the line above	CVE-2025-41244	same vendor as the line above	not named as affected at publication, now names vmware telco cloud platform	Time to revision 0 days
Wed 14 Aug 2024· 1 change
2024-08-14	CVSS base score changed	CVE-2024-22278	whole record vmware	stated at publication 5.4, now states 6.4CVSS v3.1 · base scoreMediumMedium	Time to revision 13 days
Fri 12 Jul 2024· 2 changes
2024-07-12	Product added	CVE-2024-37082	cloud foundry vmware	not named as affected at publication, now names haproxy-boshrelease	Time to revision 9 days
2024-07-12	CVSS base score changed	CVE-2024-37082	whole record vmware	stated at publication 9.0, now states 9.1CVSS v3.1 · base scoreCriticalCritical	Time to revision 9 days
Mon 11 Mar 2024· 1 change
2024-03-11	CVSS base score changed	CVE-2024-22256	whole record vmware	stated at publication 10.0, now states 4.3CVSS v3.1 · base scoreCriticalMedium	Time to revision 4 days
Fri 17 Nov 2023· 2 changes
2023-11-17	CVSS base score changed	Show all 2 CVE records in this change: CVSS base score changed: 7.5 → 7.1Hide the 2 CVE records in this change: CVSS base score changed: 7.5 → 7.1	whole record vmware	stated at publication 7.5, now states 7.1CVSS v3.1 · base scoreHighHigh	Time to revision 21 to 78 days
2023-11-17	same kind of change as the line above	CVE-2023-20900	same vendor as the line above	same change as the line above	Time to revision 78 days
2023-11-17	same kind of change as the line above	CVE-2023-34058	same vendor as the line above	same change as the line above	Time to revision 21 days
Fri 27 Oct 2023· 1 change
2023-10-27	Product added	CVE-2023-34058	vendor not named vmware	not named as affected at publication, now names open-vm-tools	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 →