Product added
| 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 3 Sep 2026· 1 record change | ||||
| 2026-09-03 | CVE-2026-58641 | not named as affected at publication, now names skiasharp | Days to revision 23 | |
| Fri 28 Aug 2026· 1 record change | ||||
| 2026-08-28 | CVE-2026-59133 | not named as affected at publication, now names microsoft hpc pack 2019 | Days to revision 17 | |
| Sun 16 Aug 2026· 1 record change | ||||
| 2026-08-16 | CVE-2026-59124 | not named as affected at publication, now names microsoft hpc pack 2019 | Days to revision 5 | |
| Thu 13 Aug 2026· 25 record changes | ||||
| 2026-08-13 | CVE-2026-65807 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68793 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68794 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68795 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68796 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68797 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68799 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68800 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68801 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68802 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68803 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68804 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68805 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68806 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68807 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68808 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68810 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68811 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68812 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68814 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68815 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68816 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-68817 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-70327 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | CVE-2026-70328 | not named as affected at publication, now names office online server | Days to revision 2 | |
| Tue 11 Aug 2026· 1 record change | ||||
| 2026-08-11 | CVE-2026-59118 | not named as affected at publication, now names copilot cowork | Days to revision 5 | |
| Sun 26 Jul 2026· 2 record changes | ||||
| 2026-07-26 | CVE-2026-48561 | not named as affected at publication, now names microsoft edge copilot for android | Days to revision 12 | |
| 2026-07-26 | CVE-2026-48561 | not named as affected at publication, now names microsoft edge copilot for ios | Days to revision 12 | |
| Wed 22 Jul 2026· 15 record changes | ||||
| 2026-07-22 | CVE-2026-47304 | not named as affected at publication, now names .net 10.0 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-47304 | not named as affected at publication, now names .net 8.0 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-47304 | not named as affected at publication, now names .net 9.0 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-47304 | not named as affected at publication, now names microsoft .net framework 4.8.1 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-50304 | not named as affected at publication, now names microsoft .net framework 4.8.1 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-50324 | not named as affected at publication, now names microsoft .net framework 4.8.1 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-50355 | not named as affected at publication, now names microsoft .net framework 4.8.1 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-50368 | not named as affected at publication, now names microsoft .net framework 4.8.1 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-50411 | not named as affected at publication, now names microsoft .net framework 4.8.1 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-50525 | not named as affected at publication, now names microsoft .net framework 4.8.1 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-50647 | not named as affected at publication, now names microsoft .net framework 4.8.1 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-50649 | not named as affected at publication, now names microsoft .net framework 4.8.1 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 4.8.1 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 4.8.1 | Days to revision 8 | |
| 2026-07-22 | CVE-2026-50659 | not named as affected at publication, now names microsoft .net framework 4.8.1 | Days to revision 8 | |
| Tue 21 Jul 2026· 3 record changes | ||||
| 2026-07-21 | CVE-2026-47304 | not named as affected at publication, now names microsoft visual studio 2017 version 15.9 (includes 15.0 - 15.8) | Days to revision 7 | |
| 2026-07-21 | CVE-2026-47304 | not named as affected at publication, now names microsoft visual studio 2019 version 16.11 (includes 16.0 - 16.10) | Days to revision 7 | |
| 2026-07-21 | CVE-2026-47304 | not named as affected at publication, now names microsoft visual studio 2026 version 18.5 | Days to revision 7 | |
| Thu 16 Jul 2026· 42 record changes | ||||
| 2026-07-16 | CVE-2026-50304 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50304 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50304 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50304 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50304 | not named as affected at publication, now names microsoft .net framework 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50324 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50324 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50324 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50324 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50324 | not named as affected at publication, now names microsoft .net framework 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50355 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50355 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50355 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50355 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50355 | not named as affected at publication, now names microsoft .net framework 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50368 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50368 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50368 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50368 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50368 | not named as affected at publication, now names microsoft .net framework 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50411 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50411 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50411 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50411 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50411 | not named as affected at publication, now names microsoft .net framework 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50647 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50647 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50647 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50647 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50647 | not named as affected at publication, now names microsoft .net framework 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 3.5 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 3.5 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Days to revision 2 | |
| 2026-07-16 | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 4.8 | Days to revision 2 | |
| Wed 15 Jul 2026· 9 record changes | ||||
| 2026-07-15 | CVE-2026-47304 | not named as affected at publication, now names microsoft .net framework 3.5 | Days to revision 1 | |
| 2026-07-15 | CVE-2026-47304 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Days to revision 1 | |
| 2026-07-15 | CVE-2026-47304 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Days to revision 1 | |
| 2026-07-15 | CVE-2026-47304 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Days to revision 1 | |
| 2026-07-15 | CVE-2026-47304 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Days to revision 1 | |
| 2026-07-15 | CVE-2026-47304 | not named as affected at publication, now names microsoft .net framework 4.8 | Days to revision 1 | |
| 2026-07-15 | CVE-2026-50525 | not named as affected at publication, now names microsoft .net framework 3.5 | Days to revision 1 | |
| 2026-07-15 | CVE-2026-50525 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Days to revision 1 | |
| 2026-07-15 | CVE-2026-50525 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Days to revision 1 | |
This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller. 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.
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 →