CVSS base score changed
| 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. | 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· 1 change | ||||
| 2026-08-27 | CVE-2026-59354 | whole record vmware | stated at publication 6.1, now states 9.6CVSS v3.1 · base scoreMediumCritical | Time to revision 0 days |
| Wed 29 Apr 2026· 2 changes | ||||
| 2026-04-29 | 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 | 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 | CVE-2026-40967 | whole record vmware | stated at publication 8.2, now states 8.6CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| Fri 27 Feb 2026· 1 change | ||||
| 2026-02-27 | CVE-2026-22716 | whole record vmware | stated at publication 2.7, now states 5.0CVSS v3.1 · base scoreLowMedium | Time to revision 0 days |
| Wed 14 Aug 2024· 1 change | ||||
| 2024-08-14 | 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· 1 change | ||||
| 2024-07-12 | 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 | 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 | 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 | CVE-2023-20900 | same vendor as the line above | same change as the line above | Time to revision 78 days |
| 2023-11-17 | CVE-2023-34058 | same vendor as the line above | same change as the line above | Time to revision 21 days |
This kind is counted once per CVE record, so changes and records are the same number here. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
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 →