Every change, newest first
These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.
| 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. |
|---|---|---|---|---|---|
| Wed 23 Aug 2023· 33 record changes | |||||
| 2023-08-23 | Fix version moved | microsoftwindows 11 version 21h2 | stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.not counted: Product line renumbered | Days to revision 189 | |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21684 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21685 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21686 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21687 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21688 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21689 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21690 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21691 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 25 more rows in this change are not listed here. Open all 33 rows → | |||||
| Wed 16 Aug 2023· 12 record changes | |||||
| 2023-08-16 | Fix version moved | microsoftmicrosoft exchange server 2016 cumulative update 23 | stated at publication 15.01.2507.031, now states 15.01.2507.032Release branch starts at 15.01.0.not counted: Build number corrected to the one that shipped | Days to revision 7 | |
| 2023-08-16 | same kind of change as the line above | CVE-2023-21709 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-35368 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-35388 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-38181 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-38182 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-38185 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | Fix version moved | microsoftmicrosoft exchange server 2019 cumulative update 12 | stated at publication 15.02.1118.036, now states 15.02.1118.037Release branch starts at 15.02.0.not counted: Build number corrected to the one that shipped | Days to revision 7 | |
| 2023-08-16 | same kind of change as the line above | CVE-2023-21709 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-35368 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-35388 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-38181 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-38182 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-38185 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| Tue 1 Aug 2023· 1 record change | |||||
| 2023-08-01 | Fix version moved | CVE-2023-28304 | microsoftmicrosoft ole db driver 18 for sql server | stated at publication 18.2.1.1, now states 18.6.5Release branch starts at 18.0.0.Original value first replaced 2023-06-17; this value first seen 2023-08-01.Not counted: Two products' boundaries swapped. 18.6.5 was the boundary of `microsoft odbc driver 18 for sql server` in the same record at publication and that entry now states 18.2.1.1 — the two values were swapped between two product entries, the same builds relabelled | Days to revision 66 |
| Tue 9 May 2023· 1 record change | |||||
| 2023-05-09 | CVSS base score changed | CVE-2023-21738 | whole record microsoft | stated at publication 7.1, now states 7.8Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 120 |
| Thu 27 Apr 2023· 2 record changes | |||||
| 2023-04-27 | CVSS base score changed | CVE-2023-21561 | whole record microsoft | stated at publication 8.8, now states 7.8Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 108 |
| 2023-04-27 | CVSS base score changed | CVE-2023-21779 | whole record microsoft | stated at publication 7.3, now states 7.8Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 108 |
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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
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 →