Every change, newest first
| 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. |
|---|---|---|---|---|---|
| Mon 6 Nov 2023· 1 change | |||||
| 2023-11-06 | CVSS base score changed | CVE-2023-38186 | whole record microsoft | stated at publication 7.8, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 90 days |
| Thu 12 Oct 2023· 1 change | |||||
| 2023-10-12 | CVSS base score changed | CVE-2023-29338 | whole record microsoft | stated at publication 5.0, now states 6.6CVSS v3.1 · base scoreMediumMedium | Time to revision 156 days |
| Tue 12 Sep 2023· 2 changes | |||||
| 2023-09-12 | Fix version moved | microsoftmicrosoft dynamics 365 (on-premises) version 9.0 | stated at publication 9.0.47.xx, now states 9.0.49.04Release branch starts at 9.0.0.same day | Time to revision 0 days | |
| 2023-09-12 | same kind of change as the line above | CVE-2023-36886 | same vendor as the line above | same change as the line aboveRelease branch starts at 9.0.0.same day | Time to revision 0 days |
| 2023-09-12 | same kind of change as the line above | CVE-2023-38164 | same vendor as the line above | same change as the line aboveRelease branch starts at 9.0.0.same day | Time to revision 0 days |
| Mon 21 Aug 2023· 1 change | |||||
| 2023-08-21 | CVSS base score changed | CVE-2023-29360 | whole record microsoft | stated at publication 7.8, now states 8.4CVSS v3.1 · base scoreHighHigh | Time to revision 69 days |
| Tue 8 Aug 2023· 1 change | |||||
| 2023-08-08 | CVSS base score changed | CVE-2023-36884 | whole record microsoft | stated at publication 0.0, now states 7.5CVSS v3.1 · base scoreNoneHighOriginal value first replaced 2023-07-31; this value first seen 2023-08-08. | Time to revision 20 days |
| Tue 1 Aug 2023· 8 changes | |||||
| 2023-08-01 | Product added | CVE-2023-28260 | not named as affected at publication, now names powershell 7.2 and 1 more | Time to revision 112 days | |
| 2023-08-01 | same kind of change as the line above | CVE-2023-28260 | same vendor as the line above | not named as affected at publication, now names powershell 7.2 | Time to revision 112 days |
| 2023-08-01 | same kind of change as the line above | CVE-2023-28260 | same vendor as the line above | not named as affected at publication, now names powershell 7.3 | Time to revision 112 days |
| 2023-08-01 | CVSS base score changed | CVE-2023-28261 | whole record microsoft | stated at publication 6.1, now states 5.7CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2023-06-17; this value first seen 2023-08-01. | Time to revision 50 days |
| 2023-08-01 | CVSS base score changed | CVE-2023-24936 | whole record microsoft | stated at publication 8.1, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 48 days |
| 2023-08-01 | CVSS base score changed | CVE-2023-32012 | whole record microsoft | stated at publication 6.3, now states 7.8CVSS v3.1 · base scoreMediumHigh | Time to revision 49 days |
| 2023-08-01 | CVSS base score changed | CVE-2023-32013 | whole record microsoft | stated at publication 6.5, now states 5.3CVSS v3.1 · base scoreMediumMedium | Time to revision 49 days |
| 2023-08-01 | CVSS base score changed | CVE-2023-32020 | whole record microsoft | stated at publication 3.7, now states 5.6CVSS v3.1 · base scoreLowMedium | Time to revision 49 days |
| 2023-08-01 | CVSS base score changed | CVE-2023-33144 | whole record microsoft | stated at publication 5.0, now states 6.6CVSS v3.1 · base scoreMediumMedium | Time to revision 49 days |
| Fri 21 Jul 2023· 1 change | |||||
| 2023-07-21 | Product added | CVE-2023-21538 | not named as affected at publication, now names powershell 7.2 | Time to revision 193 days | |
| Fri 14 Jul 2023· 4 changes | |||||
| 2023-07-14 | Product added | CVE-2023-32052 | not named as affected at publication, now names microsoft power apps | Time to revision 3 days | |
| 2023-07-14 | Product added | CVE-2023-33127 | not named as affected at publication, now names powershell 7.2 and 1 more | Time to revision 3 days | |
| 2023-07-14 | same kind of change as the line above | CVE-2023-33127 | same vendor as the line above | not named as affected at publication, now names powershell 7.2 | Time to revision 3 days |
| 2023-07-14 | same kind of change as the line above | CVE-2023-33127 | same vendor as the line above | not named as affected at publication, now names powershell 7.3 | Time to revision 3 days |
| 2023-07-14 | CVSS base score changed | CVE-2023-35348 | whole record microsoft | stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 3 days |
| Fri 30 Jun 2023· 10 changes | |||||
| 2023-06-302 commits | Product added | not named as affected at publication, now names powershell 7.2Branches and original-value intervals are stated on each row. | Time to revision 16 to 17 days | ||
| 2023-06-30 | same kind of change as the line above | CVE-2023-24895 | same vendor as the line above | same change as the line above | Time to revision 16 days |
| 2023-06-30 | same kind of change as the line above | CVE-2023-24936 | same vendor as the line above | same change as the line above | Time to revision 16 days |
| 2023-06-30 | same kind of change as the line above | CVE-2023-29331 | same vendor as the line above | same change as the line above | Time to revision 16 days |
| 2023-06-30 | same kind of change as the line above | CVE-2023-33126 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| 2023-06-30 | same kind of change as the line above | CVE-2023-24897 | same vendor as the line above | same change as the line above | Time to revision 16 days |
| 2023-06-30 | Product added | not named as affected at publication, now names powershell 7.3 | Time to revision 16 to 17 days | ||
| 2023-06-30 | same kind of change as the line above | CVE-2023-24895 | same vendor as the line above | same change as the line above | Time to revision 16 days |
| 2023-06-30 | same kind of change as the line above | CVE-2023-24936 | same vendor as the line above | same change as the line above | Time to revision 16 days |
| 2023-06-30 | same kind of change as the line above | CVE-2023-29331 | same vendor as the line above | same change as the line above | Time to revision 16 days |
| 2023-06-30 | same kind of change as the line above | CVE-2023-32032 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| 2023-06-30 | same kind of change as the line above | CVE-2023-33128 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| Sat 17 Jun 2023· 5 changes | |||||
| 2023-06-17 | CVSS base score changed | CVE-2023-23416 | whole record microsoft | stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 94 days |
| 2023-06-17 | CVSS base score changed | CVE-2023-24856 | whole record microsoft | stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHigh | Time to revision 94 days |
| 2023-06-17 | CVSS base score changed | CVE-2023-24921 | whole record microsoft | stated at publication 4.1, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 94 days |
| 2023-06-17 | CVSS base score changed | CVE-2023-28288 | whole record microsoft | stated at publication 6.5, now states 8.1CVSS v3.1 · base scoreMediumHigh | Time to revision 66 days |
| 2023-06-17 | CVSS base score changed | CVE-2023-28301 | whole record microsoft | stated at publication 4.2, now states 3.7CVSS v3.1 · base scoreMediumLow | Time to revision 66 days |
| Tue 13 Jun 2023· 1 change | |||||
| 2023-06-13 | CVSS base score changed | CVE-2023-24880 | whole record microsoft | stated at publication 5.4, now states 4.4CVSS v3.1 · base scoreMediumMedium | Time to revision 91 days |
| Mon 5 Jun 2023· 2 changes | |||||
| 2023-06-05 | Fix version moved | microsoftav1 video extension | stated at publication 1.1.51091.0, now states 1.1.60961.0Release branch starts at 1.1.0. | Time to revision 27 days | |
| 2023-06-05 | same kind of change as the line above | CVE-2023-29340 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.1.0. | Time to revision 27 days |
| 2023-06-05 | same kind of change as the line above | CVE-2023-29341 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.1.0. | Time to revision 27 days |
| Tue 9 May 2023· 1 change | |||||
| 2023-05-09 | CVSS base score changed | CVE-2023-24892 | whole record microsoft | stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHigh | Time to revision 56 days |
| Fri 28 Apr 2023· 1 change | |||||
| 2023-04-28 | Product added | CVE-2023-24934 | not named as affected at publication, now names microsoft malware protection platform | Time to revision 14 days | |
| Thu 27 Apr 2023· 3 changes | |||||
| 2023-04-27 | CVSS base score changed | CVE-2023-21807 | whole record microsoft | stated at publication 5.8, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2023-04-11; this value first seen 2023-04-27. | Time to revision 56 days |
| 2023-04-27 | CVSS base score changed | CVE-2023-24858 | whole record microsoft | stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHigh | Time to revision 44 days |
| 2023-04-27 | CVSS base score changed | CVE-2023-24911 | whole record microsoft | stated at publication 6.5, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 44 days |
| Tue 18 Apr 2023· 1 change | |||||
| 2023-04-18 | CVSS base score changed | CVE-2023-23379 | whole record microsoft | stated at publication 6.4, now states 7.8CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2023-04-14; this value first seen 2023-04-18. | Time to revision 59 days |
| Fri 14 Apr 2023· 1 change | |||||
| 2023-04-14 | CVSS base score changed | CVE-2023-28296 | whole record microsoft | stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 3 days |
| Tue 11 Apr 2023· 4 changes | |||||
| 2023-04-11 | CVSS base score changed | CVE-2023-21722 | whole record microsoft | stated at publication 4.4, now states 5.0CVSS v3.1 · base scoreMediumMedium | Time to revision 56 days |
| 2023-04-11 | CVSS base score changed | CVE-2023-21778 | whole record microsoft | stated at publication 8.3, now states 8.0CVSS v3.1 · base scoreHighHigh | Time to revision 56 days |
| 2023-04-11 | CVSS base score changed | whole record microsoft | stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 56 days | |
| 2023-04-11 | same kind of change as the line above | CVE-2023-21815 | same vendor as the line above | same change as the line above | Time to revision 56 days |
| 2023-04-11 | same kind of change as the line above | CVE-2023-23381 | same vendor as the line above | same change as the line above | Time to revision 56 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.
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 →