Every fix version that moved
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. | 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. |
|---|---|---|---|---|
| Tue 31 Dec 2024· 139 changes | ||||
| 2024-12-31 | CVE-2024-38033 | microsoft2 products | stated at publication 6.3.9600.22074, now states 6.3.9600.22318Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | CVE-2024-38033 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-38033 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | microsoftwindows 11 version 22h2 | stated at publication 10.0.22621.3435, now states 10.0.22621.3447Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | CVE-2024-20665 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-20669 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-20678 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-20693 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-21447 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26158 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26168 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26171 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 47 more rows in this change are not listed here. Open all 55 rows → | ||||
| 2024-12-31 | microsoftwindows 10 version 1507 | stated at publication 10.0.10240.20596, now states 10.0.10240.20651Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28902 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | 15 rows, one per record and product | microsoft3 products | stated at publication 10.0.14393.6897, now states 10.0.14393.6981Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 7 more rows in this change are not listed here. Open all 15 rows → | ||||
| 2024-12-31 | microsoftwindows 10 version 21h2 | stated at publication 10.0.19044.4291, now states 10.0.19044.4412Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28902 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.4291, now states 10.0.19045.4412Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28902 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | microsoftwindows 11 version 22h2 | stated at publication 10.0.22621.3435, now states 10.0.22621.3593Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28902 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | 10 rows, one per record and product | microsoft2 products | stated at publication 10.0.22631.3447, now states 10.0.22631.3593Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2 more rows in this change are not listed here. Open all 10 rows → | ||||
| 2024-12-31 | 10 rows, one per record and product | microsoft2 products | stated at publication 6.3.9600.21924, now states 6.3.9600.21972Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2 more rows in this change are not listed here. Open all 10 rows → | ||||
| 2024-12-31 | 10 rows, one per record and product | microsoft2 products | stated at publication 10.0.17763.5696, now states 10.0.17763.5820Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2 more rows in this change are not listed here. Open all 10 rows → | ||||
| 2024-12-31 | microsoftwindows server 2022 | stated at publication 10.0.20348.2402, now states 10.0.20348.2461Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28902 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | microsoftwindows server 2022, 23h2 edition (server core installation) | stated at publication 10.0.25398.830, now states 10.0.25398.887Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-28902 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-21427 | microsoft2 products | stated at publication 6.3.9600.21871, now states 6.3.9600.21924Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | CVE-2024-21427 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-21427 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-21427 | microsoft2 products | stated at publication 10.0.14393.6796, now states 10.0.14393.6897Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | CVE-2024-21427 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-21427 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-21427 | microsoft2 products | stated at publication 10.0.17763.5576, now states 10.0.17763.5696Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | CVE-2024-21427 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-21427 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-21427 | microsoftwindows server 2022 | stated at publication 10.0.20348.2340, now states 10.0.20348.2402Release branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-21427 | microsoftwindows server 2022, 23h2 edition (server core installation) | stated at publication 10.0.25398.763, now states 10.0.25398.830Release branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| Tue 10 Dec 2024· 1 change | ||||
| 2024-12-10 | CVE-2024-6156 | canonical | stated at publication 5.21.2, now states 6.1Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 5.21.2 still holds | Duration unknown |
| Tue 15 Oct 2024· 14 changes | ||||
| 2024-10-15 | CVE-2024-9137 | moxa4 products | stated at publication 3.12.1, now states 3.12.1Release branch starts at 0.not counted: Same claim, other operator | Time to revision 1 days |
| 2024-10-15 | CVE-2024-9137 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | CVE-2024-9137 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | CVE-2024-9137 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | CVE-2024-9137 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | moxanat-102 series | stated at publication 1.0.5, now states 1.0.5Release branch starts at 0.not counted: Same claim, other operator | Time to revision 1 days | |
| 2024-10-15 | CVE-2024-9137 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | CVE-2024-9139 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | moxaoncell g4302-lte4 series | stated at publication 3.9, now states 3.9Release branch starts at 0.not counted: Same claim, other operator | Time to revision 1 days | |
| 2024-10-15 | CVE-2024-9137 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | CVE-2024-9139 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | moxatn-4900 series | stated at publication 3.6, now states 3.6Release branch starts at 0.not counted: Same claim, other operator | Time to revision 1 days | |
| 2024-10-15 | CVE-2024-9137 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | CVE-2024-9139 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | CVE-2024-9139 | moxa4 products | stated at publication 3.12.1, now states 3.12.1Release branch starts at 0.not counted: Same claim, other operator | Time to revision 1 days |
| 2024-10-15 | CVE-2024-9139 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | CVE-2024-9139 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | CVE-2024-9139 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2024-10-15 | CVE-2024-9139 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| Wed 19 Jun 2024· 1 change | ||||
| 2024-06-19 | CVE-2024-0985 | vendor not namedpostgresql PostgreSQL | stated at publication 15.6, now states 16.2Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 15.6 still holds | Duration unknown |
| Wed 29 May 2024· 2 changes | ||||
| 2024-05-29 | microsoftmicrosoft dynamics 365 (on-premises) version 9.1 | stated at publication 9.1.18.xx, now states 9.1.21.05Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-05-29 | CVE-2023-36886 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-05-29 | CVE-2023-38164 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| Mon 13 May 2024· 1 change | ||||
| 2024-05-13 | CVE-2024-26817 | linuxlinux | stated at publication 6.8.6, now states 6.9Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.8.6 still holds | Duration unknown |
| Wed 8 May 2024· 1 change | ||||
| 2024-05-08 | CVE-2024-29059 | microsoftmicrosoft .net framework 3.5 | stated at publication 3.0.50727.8975, now states 3.0.50727.8976Release branch starts at 3.5.0.Not counted: Boundary below its own start. the boundary stated at publication was below the range's own start — a malformed range, not a fix anyone patched to | Time to revision 47 days |
| Mon 15 Apr 2024· 1 change | ||||
| 2024-04-15 | CVE-2024-1655 | asusexpertwifi ebm68 twcert | stated at publication 3.0.0.6.102_31933, now states 3.0.0.6.102_44384Release branch starts at earlier .Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 0 days |
| Wed 10 Apr 2024· 1 change | ||||
| 2024-04-10 | CVE-2024-29946 | splunksplunk cloud platform | stated at publication 9.1.2312.100, now states 9.1.2312.104Release branch starts at 0.Original value first replaced 2024-04-04; this value first seen 2024-04-10.Not counted: Build number corrected to the one that shipped. only the build revision moved, 13.4 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| Thu 14 Mar 2024· 2 changes | ||||
| 2024-03-14 | CVE-2024-26167 | microsoftmicrosoft edge for android | stated at publication 122.0.2365.80, now states 122.0.2365.92Release branch starts at 1.0.0.Original value first replaced 2024-03-08; this value first seen 2024-03-14.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 0 days |
| 2024-03-14 | CVE-2024-2247 | jfrogartifactory | stated at publication 7.77.7, now states 7.82.1Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.77.7 still holds | Duration unknown |
| Mon 11 Mar 2024· 1 change | ||||
| 2024-03-11 | CVE-2024-26602 | linuxlinux | stated at publication 6.7.6, now states 6.8Release branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| Wed 14 Feb 2024· 2 changes | ||||
| 2024-02-14 | red hatrhel-8 based middleware containers | stated at publication 7.6-38, now states 7.6-41Release branch starts at *.not counted: Another branch advanced | Duration unknown | |
| 2024-02-14 | CVE-2023-6134 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.6-38 still holds | Duration unknown |
| 2024-02-14 | CVE-2023-6291 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.6-38 still holds | Duration unknown |
| Fri 15 Dec 2023· 1 change | ||||
| 2023-12-15 | CVE-2023-35632 | microsoftwindows 10 version 21h2 | stated at publication 10.0.19041.3803, now states 10.0.19044.3803Release branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| Wed 13 Dec 2023· 6 changes | ||||
| 2023-12-13 | CVE-2023-5869 | red hatred hat enterprise linux 8 | stated at publication 8090020231114113712.a75119d5, now states 8090020231201202407.a75119d5Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8090020231114113712.a75119d5 still holds | Duration unknown |
| 2023-12-13 | CVE-2023-5869 | red hat3 products | stated at publication 8020020231128165246.4cda2c84, now states 8020020231201202149.4cda2c84Release branch starts at *.not counted: Another branch advanced | Duration unknown |
| 2023-12-13 | CVE-2023-5869 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8020020231128165246.4cda2c84 still holds | Duration unknown |
| 2023-12-13 | CVE-2023-5869 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8020020231128165246.4cda2c84 still holds | Duration unknown |
| 2023-12-13 | CVE-2023-5869 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8020020231128165246.4cda2c84 still holds | Duration unknown |
| 2023-12-13 | CVE-2023-5869 | red hatred hat enterprise linux 8.6 extended update support | stated at publication 8060020231128165328.ad008a3a, now states 8060020231201202249.ad008a3aRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8060020231128165328.ad008a3a still holds | Duration unknown |
| 2023-12-13 | CVE-2023-5869 | red hatred hat enterprise linux 8.8 extended update support | stated at publication 8080020231128165335.63b34585, now states 8080020231201202316.63b34585Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8080020231128165335.63b34585 still holds | Duration unknown |
| Mon 11 Dec 2023· 2 changes | ||||
| 2023-12-11 | red hatred hat enterprise linux 8 | stated at publication 8090020231114113712.a75119d5, now states 8090020231128173330.a75119d5Release branch starts at *.not counted: Another branch advanced | Duration unknown | |
| 2023-12-11 | CVE-2023-5868 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8090020231114113712.a75119d5 still holds | Duration unknown |
| 2023-12-11 | CVE-2023-5870 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8090020231114113712.a75119d5 still holds | Duration unknown |
| Wed 6 Dec 2023· 1 change | ||||
| 2023-12-06 | CVE-2023-45283 | go standard librarypath/filepath Go | stated at publication 1.21.4, now states 1.21.5Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 1.21.4 still holds | Duration unknown |
| Wed 22 Nov 2023· 54 changes | ||||
| 2023-11-22 | microsoftwindows 11 version 22h3 | stated at publication 10.0.22621.2715, now states 10.0.22631.2715Release branch starts at *.not counted: Product line renumbered | Duration unknown | |
| 2023-11-22 | CVE-2023-36017 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36025 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36028 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36033 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36036 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36046 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36047 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36393 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 16 more rows in this change are not listed here. Open all 24 rows → | ||||
| 2023-11-22 | microsoftwindows 11 version 23h2 | stated at publication 10.0.22621.2715, now states 10.0.22631.2715Release branch starts at *.not counted: Product line renumbered | Duration unknown | |
| 2023-11-22 | CVE-2023-36017 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36025 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36028 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36033 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36036 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36046 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36047 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 2023-11-22 | CVE-2023-36393 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| 15 more rows in this change are not listed here. Open all 23 rows → | ||||
| 2023-11-22 | mozillafirefox | stated at publication 115.5, now states 120Release branch starts at 0.not counted: Description already named the later value | Time to revision 1 days | |
| 2023-11-22 | CVE-2023-6204 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 1 days |
| 2023-11-22 | CVE-2023-6205 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 1 days |
| 2023-11-22 | CVE-2023-6206 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 1 days |
| 2023-11-22 | CVE-2023-6207 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 1 days |
| 2023-11-22 | CVE-2023-6208 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 1 days |
| 2023-11-22 | CVE-2023-6209 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 1 days |
| 2023-11-22 | CVE-2023-6212 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 1 days |
| Tue 14 Nov 2023· 2 changes | ||||
| 2023-11-14 | red hatred hat enterprise linux 8 | stated at publication 8080020231030214932.63b34585, now states 8090020231030224841.a75119d5Release branch starts at *.not counted: Another branch advanced | Duration unknown | |
| 2023-11-14 | CVE-2023-46846 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8080020231030214932.63b34585 still holds | Duration unknown |
| 2023-11-14 | CVE-2023-46847 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8080020231030214932.63b34585 still holds | Duration unknown |
| Wed 4 Oct 2023· 1 change | ||||
| 2023-10-04 | CVE-2023-4571 | splunksplunk itsi | stated at publication 4.15.3, now states 4.17.1Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 4.15.3 still holds | Duration unknown |
| Fri 8 Sep 2023· 1 change | ||||
| 2023-09-08 | CVE-2023-4369 | googlechrome Chrome | stated at publication 116.0.5845.96, now states 116.0.5845.120Release branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| Wed 23 Aug 2023· 33 changes | ||||
| 2023-08-23 | 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 | Time to revision 189 days | |
| 2023-08-23 | 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 | Time to revision 189 days |
| 2023-08-23 | 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 | Time to revision 189 days |
| 2023-08-23 | 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 | Time to revision 189 days |
| 2023-08-23 | 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 | Time to revision 189 days |
| 2023-08-23 | 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 | Time to revision 189 days |
| 2023-08-23 | 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 | Time to revision 189 days |
| 2023-08-23 | 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 | Time to revision 189 days |
| 2023-08-23 | 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 | Time to revision 189 days |
| 25 more rows in this change are not listed here. Open all 33 rows → | ||||
| Wed 16 Aug 2023· 12 changes | ||||
| 2023-08-16 | 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 | Time to revision 7 days | |
| 2023-08-16 | 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 | Time to revision 7 days |
| 2023-08-16 | 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 | Time to revision 7 days |
| 2023-08-16 | 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 | Time to revision 7 days |
| 2023-08-16 | 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 | Time to revision 7 days |
| 2023-08-16 | 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 | Time to revision 7 days |
| 2023-08-16 | 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 | Time to revision 7 days |
| 2023-08-16 | 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 | Time to revision 7 days | |
| 2023-08-16 | 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 | Time to revision 7 days |
| 2023-08-16 | 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 | Time to revision 7 days |
| 2023-08-16 | 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 | Time to revision 7 days |
| 2023-08-16 | 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 | Time to revision 7 days |
| 2023-08-16 | 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 | Time to revision 7 days |
| 2023-08-16 | 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 | Time to revision 7 days |
| Fri 4 Aug 2023· 3 changes | ||||
| 2023-08-04 | googlechrome Chrome | stated at publication 115.0.5790.98, now states 115.0.5790.131Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2023-08-04 | CVE-2023-3729 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2023-08-04 | CVE-2023-3731 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2023-08-04 | CVE-2023-3739 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| Tue 1 Aug 2023· 1 change | ||||
| 2023-08-01 | 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 | Time to revision 66 days |
| Thu 27 Jul 2023· 18 changes | ||||
| 2023-07-272 commits | appletvos | stated at publication 13.2, now states 16.3Branches and original-value intervals are stated on each row.not counted: Description already named the later value | Time to revision 150 days | |
| 2023-07-27 | CVE-2023-23496 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-23500 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-23503 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-23511 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-23517 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-23519 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-23502 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-23518 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | appletvos | stated at publication 15.7, now states 16.3Release branch starts at 0.not counted: Description already named the later value | Time to revision 150 days | |
| 2023-07-27 | CVE-2023-23500 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-23503 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-272 commits | appletvos | stated at publication 12.6, now states 16.3Branches and original-value intervals are stated on each row.not counted: Description already named the later value | Time to revision 150 days | |
| 2023-07-27 | CVE-2023-23511 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-23517 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-23502 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-23518 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-272 commits | appletvos | stated at publication 11.7, now states 16.3Branches and original-value intervals are stated on each row.not counted: Description already named the later value | Time to revision 150 days | |
| 2023-07-27 | CVE-2023-23517 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-23518 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-27 | CVE-2023-28206 | appleios and ipados | stated at publication 15.7, now states 16.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 15.7 still holds | Duration unknown |
| 2023-07-27 | CVE-2023-23514 | applemacos | stated at publication 13.2, now states 13.3Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 13.2 still holds | Duration unknown |
| Wed 26 Jul 2023· 9 changes | ||||
| 2023-07-26 | CVE-2023-23499 | appletvos | stated at publication 11.7, now states 16.3Release branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-26 | appletvos | stated at publication 12.6, now states 16.3Release branch starts at 0.not counted: Description already named the later value | Time to revision 150 days | |
| 2023-07-26 | CVE-2023-23499 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-26 | CVE-2023-23504 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-26 | appletvos | stated at publication 13.2, now states 16.3Release branch starts at 0.not counted: Description already named the later value | Time to revision 150 days | |
| 2023-07-26 | CVE-2023-23499 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-26 | CVE-2023-23504 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-26 | CVE-2023-23512 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-26 | CVE-2023-23504 | appletvos | stated at publication 15.7, now states 16.3Release branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 150 days |
| 2023-07-26 | CVE-2023-37450 | applemacos | stated at publication 13.4, now states 13.5Release branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 0 days |
| 2023-07-26 | CVE-2023-28205 | appleios and ipados | stated at publication 15.7, now states 16.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 15.7 still holds | Duration unknown |
| Thu 15 Jun 2023· 1 change | ||||
| 2023-06-15 | CVE-2023-0009 | palo alto networksglobalprotect app palo_alto | stated at publication 6.1.1, now states 6.2Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.1.1 still holds | Duration unknown |
| Wed 24 May 2023· 1 change | ||||
| 2023-05-24 | CVE-2023-2597 | eclipse foundationeclipse openj9 eclipse | stated at publication 0.37.0, now states 0.37.0Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 2 days |
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. 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 →