Skip to content

Every change, newest first

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

20 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
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.KindRecord, 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 changedDays 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 record changes
2026-08-27Product addedCVE-2026-59323vmwarenot named as affected at publication, now names micrometer tracingDays to revision 6
2026-08-27CVSS base score changedCVE-2026-59354
whole record
vmware
stated at publication 6.1, now states 9.6CVSS v3.1 · base scoreMediumCriticalDays to revision 0
Tue 23 Jun 2026· 1 record change
2026-06-23Fix version movedCVE-2026-41715
springreactor netty
vmware
stated at publication 1.3.6, now states 1.3.15.1Release branch starts at 1.3.0.Days to revision 15
Wed 29 Apr 2026· 2 record changes
2026-04-29CVSS base score changedCVE-2026-22740
whole record
vmware
stated at publication 0.0, now states 6.5CVSS v3.1 · base scoreNoneMediumDays to revision 0
2026-04-29CVSS base score changedCVE-2026-22741
whole record
vmware
stated at publication 0.0, now states 3.1CVSS v3.1 · base scoreNoneLowDays to revision 0
Tue 28 Apr 2026· 1 record change
2026-04-28CVSS base score changedCVE-2026-40967
whole record
vmware
stated at publication 8.2, now states 8.6CVSS v3.1 · base scoreHighHighDays to revision 0
Tue 14 Apr 2026· 1 record change
2026-04-14Product addedCVE-2026-22719not named as affected at publication, now names vmware cloud foundation operationsDays to revision 48
Fri 27 Feb 2026· 1 record change
2026-02-27CVSS base score changedCVE-2026-22716
whole record
vmware
stated at publication 2.7, now states 5.0CVSS v3.1 · base scoreLowMediumDays to revision 0
Mon 29 Sep 2025· 5 record changes
2025-09-29Product addedCVE-2025-41250not named as affected at publication, now names vsphere foundationDays to revision 0
2025-09-29Product addedCVE-2025-41244not named as affected at publication, now names vmware aria operationsDays to revision 0
2025-09-29Product addedCVE-2025-41244not named as affected at publication, now names vmware cloud foundationDays to revision 0
2025-09-29Product addedCVE-2025-41244not named as affected at publication, now names vmware telco cloud infrastructureDays to revision 0
2025-09-29Product addedCVE-2025-41244not named as affected at publication, now names vmware telco cloud platformDays to revision 0
Wed 14 Aug 2024· 1 record change
2024-08-14CVSS base score changedCVE-2024-22278
whole record
vmware
stated at publication 5.4, now states 6.4CVSS v3.1 · base scoreMediumMediumDays to revision 13
Fri 12 Jul 2024· 2 record changes
2024-07-12Product addedCVE-2024-37082vmwarenot named as affected at publication, now names haproxy-boshreleaseDays to revision 9
2024-07-12CVSS base score changedCVE-2024-37082
whole record
vmware
stated at publication 9.0, now states 9.1CVSS v3.1 · base scoreCriticalCriticalDays to revision 9
Mon 11 Mar 2024· 1 record change
2024-03-11CVSS base score changedCVE-2024-22256
whole record
vmware
stated at publication 10.0, now states 4.3CVSS v3.1 · base scoreCriticalMediumDays to revision 4
Fri 17 Nov 2023· 2 record changes
2023-11-17CVSS base score changedCVE-2023-20900
whole record
vmware
stated at publication 7.5, now states 7.1CVSS v3.1 · base scoreHighHighDays to revision 78
2023-11-17CVSS base score changedCVE-2023-34058
whole record
vmware
stated at publication 7.5, now states 7.1CVSS v3.1 · base scoreHighHighDays to revision 21
Fri 27 Oct 2023· 1 record change
2023-10-27Product addedCVE-2023-34058
vendor not named
vmware
not named as affected at publication, now names open-vm-toolsDays 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.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 03:47 UTC · scroll for earlierfewermore

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 →