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. |
|---|---|---|---|---|---|
| Tue 1 Sep 2026· 6 changes | |||||
| 2026-09-01 | Forensic triage now required | CVE-2019-1068 | MicrosoftSQL Server CISA KEV | stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Time to revision 6 days |
| 2026-09-01 | Forensic triage now required | MicrosoftSharePoint | stated at publication not stated, now states Yesnot counted: The prior instruction already required triage | Time to revision 14 to 47 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-55040 | same vendor as the line above | same change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Time to revision 14 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-50522 | same vendor as the line above | same change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Time to revision 41 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-58644 | same vendor as the line above | same change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Time to revision 47 days |
| 2026-09-01 | Forensic triage now required | MicrosoftSharePoint Server | stated at publication not stated, now states Yesnot counted: The prior instruction already required triage | Time to revision 49 to 62 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-56164 | same vendor as the line above | same change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Time to revision 49 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-45659 | same vendor as the line above | same change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Time to revision 62 days |
| Fri 21 Aug 2026· 2 changes | |||||
| 2026-08-21 | Fix version moved | CVE-2026-54981 | microsoftpython extension for visual studio code | stated at publication 1.132.1, now states 2026.3.1Release branch starts at 2020.Not counted: Version scheme changed. one side is on a calendar versioning scheme and the other is not — the two are not comparable in either direction | Time to revision 10 days |
| 2026-08-21 | Removed from CISA KEV | CVE-2026-69836 | MicrosoftEntra ID CISA KEV | Previously listed from 2026-08-21Not counted: Same-day catalog correction. entry stood 1.2 hours before being withdrawn — a same-day catalog correction, not a KEV listing anyone escalated | Time to revision 0 days |
| Tue 18 Aug 2026· 1 change | |||||
| 2026-08-18 | Product added | CVE-2026-47632 | not named as affected at publication, now names azure connected machine agentNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed microsoft/azure monitor agent metrics extension; a new product identity is not established | Time to revision 35 days | |
| Sun 16 Aug 2026· 6 changes | |||||
| 2026-08-16 | Fix version moved | CVE-2026-42976 | microsoft3 products | stated at publication 10.0.17763.8880, now states 10.0.17763.9121Release branch starts at 10.0.17763.0.Original value first replaced 2026-08-12; this value first seen 2026-08-16.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-16 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Original value first replaced 2026-08-12; this value first seen 2026-08-16.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.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 1 days |
| 2026-08-16 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Original value first replaced 2026-08-12; this value first seen 2026-08-16.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.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 1 days |
| 2026-08-16 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Original value first replaced 2026-08-12; this value first seen 2026-08-16.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.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 1 days |
| 2026-08-16 | Fix version moved | CVE-2026-49179 | microsoft3 products | stated at publication 10.0.17763.9115, now states 10.0.17763.9121Release branch starts at 10.0.17763.0.not counted: Build number corrected to the one that shipped | Time to revision 5 days |
| 2026-08-16 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.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 5 days |
| 2026-08-16 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.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 5 days |
| 2026-08-16 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.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 5 days |
| Wed 12 Aug 2026· 12 changes | |||||
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoft3 products | stated at publication 10.0.14393.9234, now states 10.0.14393.9418Release branch starts at 10.0.14393.0.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoftwindows 10 version 21h2 | stated at publication 10.0.19044.7417, now states 10.0.19044.7663Release branch starts at 10.0.19044.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7417, now states 10.0.19045.7663Release branch starts at 10.0.19045.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2704Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoft2 products | stated at publication 6.2.9200.26132, now states 6.2.9200.26280Release branch starts at 6.2.9200.0.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoft2 products | stated at publication 6.3.9600.23228, now states 6.3.9600.23338Release branch starts at 6.3.9600.0.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoft2 products | stated at publication 10.0.26100.32995, now states 10.0.26100.33296Release branch starts at 10.0.26100.0.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| Tue 11 Aug 2026· 4 changes | |||||
| 2026-08-11 | Fix version moved | CVE-2026-49179 | microsoft2 products | stated at publication 6.2.9200.26279, now states 6.2.9200.26280Release branch starts at 6.2.9200.0.not counted: Build number corrected to the one that shipped | Time to revision 0 days |
| 2026-08-11 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 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 |
| 2026-08-11 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 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 |
| 2026-08-11 | Fix version moved | CVE-2026-49179 | microsoft2 products | stated at publication 6.3.9600.23337, now states 6.3.9600.23338Release branch starts at 6.3.9600.0.not counted: Build number corrected to the one that shipped | Time to revision 0 days |
| 2026-08-11 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 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 |
| 2026-08-11 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 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 22 Jul 2026· 191 changes | |||||
| 2026-07-22 | Fix version moved | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.not counted: Build number corrected to the one that shipped | Time to revision 8 days | |
| 2026-07-22 | same kind of change as the line above | CVE-2026-33842 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 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 |
| 2026-07-22 | same kind of change as the line above | CVE-2026-34328 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 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 |
| 2026-07-22 | same kind of change as the line above | CVE-2026-34346 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 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 |
| 2026-07-22 | same kind of change as the line above | CVE-2026-34348 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 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 |
| 2026-07-22 | same kind of change as the line above | CVE-2026-34349 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 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 |
| 2026-07-22 | same kind of change as the line above | CVE-2026-40378 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 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 |
| 2026-07-22 | same kind of change as the line above | CVE-2026-40422 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 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 |
| 2026-07-22 | same kind of change as the line above | CVE-2026-41087 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 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 |
| 183 more rows in this change are not listed here. Open all 191 rows → | |||||
| Tue 9 Jun 2026· 37 changes | |||||
| 2026-06-09 | Fix version moved | microsoftwindows 11 version 23h2 | stated at publication 10.0.22631.7079, now states 10.0.22631.7219Release branch starts at *.not counted: Another branch advanced | Duration unknown | |
| 2026-06-09 | same kind of change as the line above | CVE-2026-21530 | 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 10.0.22631.7079 still holds | Duration unknown |
| 2026-06-09 | same kind of change as the line above | CVE-2026-32161 | 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 10.0.22631.7079 still holds | Duration unknown |
| 2026-06-09 | same kind of change as the line above | CVE-2026-32170 | 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 10.0.22631.7079 still holds | Duration unknown |
| 2026-06-09 | same kind of change as the line above | CVE-2026-32209 | 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 10.0.22631.7079 still holds | Duration unknown |
| 2026-06-09 | same kind of change as the line above | CVE-2026-33834 | 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 10.0.22631.7079 still holds | Duration unknown |
| 2026-06-09 | same kind of change as the line above | CVE-2026-33835 | 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 10.0.22631.7079 still holds | Duration unknown |
| 2026-06-09 | same kind of change as the line above | CVE-2026-33837 | 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 10.0.22631.7079 still holds | Duration unknown |
| 2026-06-09 | same kind of change as the line above | CVE-2026-33838 | 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 10.0.22631.7079 still holds | Duration unknown |
| 29 more rows in this change are not listed here. Open all 37 rows → | |||||
| Fri 22 May 2026· 1 change | |||||
| 2026-05-22 | Fix version moved | CVE-2026-32185 | microsoftmicrosoft teams for android | stated at publication 1.0.0.2026092103, now states 1.0.0.2026092402Release branch starts at 1.0.0.Original value first replaced 2026-05-18; this value first seen 2026-05-22.Not counted: Build number corrected to the one that shipped. only the build revision moved, 10.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 6 days |
| Mon 11 May 2026· 1 change | |||||
| 2026-05-11 | Product added | CVE-2026-32226 | not named as affected at publication, now names microsoft .net framework 3.5Not counted: Already named at publication. already named at publication inside microsoft/microsoft .net framework 3.5 and 4.7.2 — the record spelled this product out all along | Time to revision 27 days | |
| Thu 16 Apr 2026· 1 change | |||||
| 2026-04-16 | Fix version moved | CVE-2025-64669 | microsoftwindows admin center | stated at publication 2.5.1.49, now states 2.6.5.16Release branch starts at 1809.0.Original value first replaced 2025-12-11; this value first seen 2026-04-16.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 0 days |
| Fri 23 Jan 2026· 2 changes | |||||
| 2026-01-23 | Fix version moved | CVE-2026-20805 | microsoft2 products | stated at publication 10.0.26100.7623, now states 10.0.26100.32230Release branch starts at 10.0.26100.0.not counted: Build number corrected to the one that shipped | Time to revision 10 days |
| 2026-01-23 | same kind of change as the line above | CVE-2026-20805 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 10.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 10 days |
| 2026-01-23 | same kind of change as the line above | CVE-2026-20805 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 10.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 10 days |
| Tue 20 Jan 2026· 8 changes | |||||
| 2026-01-202 commits | Fix version moved | 8 rows, one per record and product | microsoft2 products | stated at publication 10.0.26100.7623, now states 10.0.26100.32230Branches and original-value intervals are stated on each row.not counted: 2 classes | Time to revision 7 days |
| 2026-01-20 | same kind of change as the line above | CVE-2026-20818 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.2 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 |
| 2026-01-20 | same kind of change as the line above | CVE-2026-20818 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.2 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 |
| 2026-01-20 | same kind of change as the line above | CVE-2026-20830 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.2 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 |
| 2026-01-20 | same kind of change as the line above | CVE-2026-20830 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.2 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 |
| 2026-01-20 | same kind of change as the line above | CVE-2026-20848 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.2 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 |
| 2026-01-20 | same kind of change as the line above | CVE-2026-20848 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.2 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 |
| 2026-01-20 | same kind of change as the line above | CVE-2026-21221 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Two products' boundaries swapped. 10.0.26100.32230 was the boundary of `windows 11 version 24h2` in the same record at publication and that entry now states 10.0.26100.7623 — the two values were swapped between two product entries, the same builds relabelled | Time to revision 7 days |
| 2026-01-20 | same kind of change as the line above | CVE-2026-21221 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Two products' boundaries swapped. 10.0.26100.32230 was the boundary of `windows 11 version 24h2` in the same record at publication and that entry now states 10.0.26100.7623 — the two values were swapped between two product entries, the same builds relabelled | Time to revision 7 days |
| Wed 17 Dec 2025· 8 changes | |||||
| 2025-12-17 | KEV due date moved | CVE-2021-34527 | MicrosoftWindows CISA KEV | stated at publication 2021-07-20, now states 2022-05-03Not counted: Due date backfilled into the past. the new due date 2022-05-03 was already in the past on 2025-12-17, so no live compliance date moved | Duration unknown |
| 2025-12-17 | KEV due date moved | CVE-2020-1350 | MicrosoftWindows CISA KEV | stated at publication 2020-07-24, now states 2022-05-03Not counted: Due date backfilled into the past. the new due date 2022-05-03 was already in the past on 2025-12-17, so no live compliance date moved | Duration unknown |
| 2025-12-17 | KEV due date moved | CVE-2020-1472 | MicrosoftNetlogon CISA KEV | stated at publication 2020-09-21, now states 2022-05-03Not counted: Due date backfilled into the past. the new due date 2022-05-03 was already in the past on 2025-12-17, so no live compliance date moved | Duration unknown |
| 2025-12-17 | KEV due date moved | MicrosoftExchange Server | stated at publication 2021-04-16, now states 2022-05-03not counted: Due date backfilled into the past | Duration unknown | |
| 2025-12-17 | same kind of change as the line above | CVE-2021-26855 | same vendor as the line above | same change as the line aboveNot counted: Due date backfilled into the past. the new due date 2022-05-03 was already in the past on 2025-12-17, so no live compliance date moved | Duration unknown |
| 2025-12-17 | same kind of change as the line above | CVE-2021-26858 | same vendor as the line above | same change as the line aboveNot counted: Due date backfilled into the past. the new due date 2022-05-03 was already in the past on 2025-12-17, so no live compliance date moved | Duration unknown |
| 2025-12-17 | same kind of change as the line above | CVE-2021-27065 | same vendor as the line above | same change as the line aboveNot counted: Due date backfilled into the past. the new due date 2022-05-03 was already in the past on 2025-12-17, so no live compliance date moved | Duration unknown |
| 2025-12-17 | same kind of change as the line above | CVE-2021-26857 | same vendor as the line above | same change as the line aboveNot counted: Due date backfilled into the past. the new due date 2022-05-03 was already in the past on 2025-12-17, so no live compliance date moved | Duration unknown |
| 2025-12-17 | KEV due date moved | CVE-2020-0601 | MicrosoftWindows CISA KEV | stated at publication 2020-01-29, now states 2022-05-03Not counted: Due date backfilled into the past. the new due date 2022-05-03 was already in the past on 2025-12-17, so no live compliance date moved | Duration unknown |
| Thu 23 Oct 2025· 12 changes | |||||
| 2025-10-23 | Fix version moved | CVE-2025-59287 | microsoft2 products | stated at publication 6.2.9200.25722, now states 6.2.9200.25728Release branch starts at 6.2.9200.0.not counted: Build number corrected to the one that shipped | Time to revision 9 days |
| 2025-10-23 | same kind of change as the line above | CVE-2025-59287 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 9.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 9 days |
| 2025-10-23 | same kind of change as the line above | CVE-2025-59287 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 9.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 9 days |
| 2025-10-23 | Fix version moved | CVE-2025-59287 | microsoft2 products | stated at publication 6.3.9600.22824, now states 6.3.9600.22826Release branch starts at 6.3.9600.0.not counted: Build number corrected to the one that shipped | Time to revision 9 days |
| 2025-10-23 | same kind of change as the line above | CVE-2025-59287 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 9.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 9 days |
| 2025-10-23 | same kind of change as the line above | CVE-2025-59287 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 9.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 9 days |
| 2025-10-23 | Fix version moved | CVE-2025-59287 | microsoft2 products | stated at publication 10.0.14393.8519, now states 10.0.14393.8524Release branch starts at 10.0.14393.0.not counted: Build number corrected to the one that shipped | Time to revision 9 days |
| 2025-10-23 | same kind of change as the line above | CVE-2025-59287 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 9.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 9 days |
| 2025-10-23 | same kind of change as the line above | CVE-2025-59287 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 9.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 9 days |
| 2025-10-23 | Fix version moved | CVE-2025-59287 | microsoft2 products | stated at publication 10.0.17763.7919, now states 10.0.17763.7922Release branch starts at 10.0.17763.0.not counted: Build number corrected to the one that shipped | Time to revision 9 days |
| 2025-10-23 | same kind of change as the line above | CVE-2025-59287 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 9.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 9 days |
| 2025-10-23 | same kind of change as the line above | CVE-2025-59287 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 9.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 9 days |
| 2025-10-23 | Fix version moved | CVE-2025-59287 | microsoftwindows server 2022 | stated at publication 10.0.20348.4294, now states 10.0.20348.4297Release branch starts at 10.0.20348.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 9.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 9 days |
| 2025-10-23 | Fix version moved | CVE-2025-59287 | microsoftwindows server 2022, 23h2 edition (server core installation) | stated at publication 10.0.25398.1913, now states 10.0.25398.1916Release branch starts at 10.0.25398.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 9.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 9 days |
| 2025-10-23 | Fix version moved | CVE-2025-59287 | microsoft2 products | stated at publication 10.0.26100.6899, now states 10.0.26100.6905Release branch starts at 10.0.26100.0.not counted: Build number corrected to the one that shipped | Time to revision 9 days |
| 2025-10-23 | same kind of change as the line above | CVE-2025-59287 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 9.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 9 days |
| 2025-10-23 | same kind of change as the line above | CVE-2025-59287 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 9.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 9 days |
| Fri 17 Oct 2025· 1 change | |||||
| 2025-10-17 | Product added | CVE-2025-59033 | mitre | not named as affected at publication, now names windowsNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Time to revision 40 days |
| Tue 14 Oct 2025· 16 changes | |||||
| 2025-10-14 | Fix version moved | CVE-2024-30098 | microsoftwindows 10 version 1507 | stated at publication 10.0.10240.20710, now states 10.0.10240.21161Release 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 |
| 2025-10-14 | Fix version moved | CVE-2024-30098 | microsoft3 products | stated at publication 10.0.14393.7159, now states 10.0.14393.8519Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2025-10-14 | same kind of change as the line above | CVE-2024-30098 | 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 |
| 2025-10-14 | same kind of change as the line above | CVE-2024-30098 | 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 |
| 2025-10-14 | same kind of change as the line above | CVE-2024-30098 | 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 |
| 2025-10-14 | Fix version moved | CVE-2024-30098 | microsoft3 products | stated at publication 10.0.17763.6054, now states 10.0.17763.7919Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2025-10-14 | same kind of change as the line above | CVE-2024-30098 | 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 |
| 2025-10-14 | same kind of change as the line above | CVE-2024-30098 | 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 |
| 2025-10-14 | same kind of change as the line above | CVE-2024-30098 | 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 |
| 2025-10-14 | Fix version moved | CVE-2024-30098 | microsoftwindows 10 version 21h2 | stated at publication 10.0.19044.4651, now states 10.0.19044.6456Release 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 |
| 2025-10-14 | Fix version moved | CVE-2024-30098 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.4651, now states 10.0.19045.6456Release 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 |
| 2025-10-14 | Fix version moved | CVE-2024-30098 | microsoftwindows 11 version 22h2 | stated at publication 10.0.22621.3880, now states 10.0.22621.6060Release 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 |
| 2025-10-14 | Fix version moved | CVE-2024-30098 | microsoft2 products | stated at publication 10.0.22631.3880, now states 10.0.22631.6060Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2025-10-14 | same kind of change as the line above | CVE-2024-30098 | 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 |
| 2025-10-14 | same kind of change as the line above | CVE-2024-30098 | 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 |
| 2025-10-14 | Fix version moved | CVE-2024-30098 | microsoft2 products | stated at publication 6.3.9600.22074, now states 6.3.9600.22824Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2025-10-14 | same kind of change as the line above | CVE-2024-30098 | 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 |
| 2025-10-14 | same kind of change as the line above | CVE-2024-30098 | 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 |
| 2025-10-14 | Fix version moved | CVE-2024-30098 | microsoftwindows server 2022 | stated at publication 10.0.20348.2582, now states 10.0.20348.4294Release 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 |
| 2025-10-14 | Fix version moved | CVE-2024-30098 | microsoftwindows server 2022, 23h2 edition (server core installation) | stated at publication 10.0.25398.1009, now states 10.0.25398.1913Release 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 9 Sep 2025· 3 changes | |||||
| 2025-09-09 | Fix version moved | CVE-2025-48807 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19044.6093, now states 10.0.19045.6332Release branch starts at 10.0.19045.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 28 days |
| 2025-09-09 | Fix version moved | CVE-2025-48807 | microsoft2 products | stated at publication 10.0.22621.5624, now states 10.0.22631.5909Release branch starts at 10.0.22631.0.not counted: Boundary below its own start | Time to revision 28 days |
| 2025-09-09 | same kind of change as the line above | CVE-2025-48807 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.22631.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 28 days |
| 2025-09-09 | same kind of change as the line above | CVE-2025-48807 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.22631.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 28 days |
| Sat 23 Aug 2025· 2 changes | |||||
| 2025-08-23 | Fix version moved | microsoftmicrosoft sql server 2022 (cu 19) | stated at publication 16.0.1140.6, now states 16.0.4200.1Release branch starts at 16.0.0.0.not counted: Two products' boundaries swapped | Time to revision 45 days | |
| 2025-08-23 | same kind of change as the line above | CVE-2025-49717 | same vendor as the line above | same change as the line aboveRelease branch starts at 16.0.0.0.Not counted: Two products' boundaries swapped. 16.0.4200.1 was the boundary of `microsoft sql server 2022 (gdr)` in the same record at publication and that entry now states 16.0.1140.6 — the two values were swapped between two product entries, the same builds relabelled | Time to revision 45 days |
| 2025-08-23 | same kind of change as the line above | CVE-2025-49718 | same vendor as the line above | same change as the line aboveRelease branch starts at 16.0.0.0.Not counted: Two products' boundaries swapped. 16.0.4200.1 was the boundary of `microsoft sql server 2022 (gdr)` in the same record at publication and that entry now states 16.0.1140.6 — the two values were swapped between two product entries, the same builds relabelled | Time to revision 45 days |
| Tue 5 Aug 2025· 1 change | |||||
| 2025-08-05 | Fix version moved | CVE-2025-49719 | microsoftmicrosoft sql server 2022 (cu 19) | stated at publication 16.0.1140.6, now states 16.0.4200.1Release branch starts at 16.0.0.0.Not counted: Two products' boundaries swapped. 16.0.4200.1 was the boundary of `microsoft sql server 2022 (gdr)` in the same record at publication and that entry now states 16.0.1140.6 — the two values were swapped between two product entries, the same builds relabelled | Time to revision 28 days |
| Fri 18 Jul 2025· 1 change | |||||
| 2025-07-18 | Fix version moved | CVE-2025-49735 | microsoftwindows server 2022, 23h2 edition (server core installation) | stated at publication 10.0.22621.5472, now states 10.0.25398.1665Release branch starts at 10.0.25398.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 10 days |
| Tue 15 Jul 2025· 2 changes | |||||
| 2025-07-15 | Fix version moved | CVE-2025-49735 | microsoft2 products | stated at publication 10.0.10240.21034, now states 10.0.17763.7434Release branch starts at 10.0.17763.0.not counted: Boundary below its own start | Time to revision 7 days |
| 2025-07-15 | same kind of change as the line above | CVE-2025-49735 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.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 7 days |
| 2025-07-15 | same kind of change as the line above | CVE-2025-49735 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.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 7 days |
| Thu 10 Jul 2025· 10 changes | |||||
| 2025-07-10 | Fix version moved | CVE-2023-24932 | microsoftwindows 10 version 1507 | stated at publication 10.0.10240.19926, now states 10.0.10240.21073Release 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 |
| 2025-07-10 | Fix version moved | CVE-2023-24932 | microsoft2 products | stated at publication 10.0.14393.5921, now states 10.0.14393.8246Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2025-07-10 | same kind of change as the line above | CVE-2023-24932 | 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 |
| 2025-07-10 | same kind of change as the line above | CVE-2023-24932 | 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 |
| 2025-07-10 | Fix version moved | CVE-2023-24932 | microsoftwindows 10 version 21h2 | stated at publication 10.0.19044.2965, now states 10.0.19044.6093Release 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 |
| 2025-07-10 | Fix version moved | CVE-2023-24932 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.2965, now states 10.0.19045.6093Release 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 |
| 2025-07-10 | Fix version moved | CVE-2023-24932 | microsoftwindows 11 version 22h2 | stated at publication 10.0.22000.1702, now states 10.0.22621.5624Release 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 |
| 2025-07-10 | Fix version moved | CVE-2023-24932 | microsoftwindows server 2012 | stated at publication 6.2.9200.24266, now states 6.2.9200.25573Release 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 |
| 2025-07-10 | Fix version moved | CVE-2023-24932 | microsoftwindows server 2012 r2 | stated at publication 6.3.9600.20969, now states 6.3.9600.22676Release 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 |
| 2025-07-10 | Fix version moved | CVE-2023-24932 | microsoftwindows server 2019 | stated at publication 10.0.17763.4377, now states 10.0.17763.7558Release 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 |
| 2025-07-10 | Fix version moved | CVE-2023-24932 | microsoftwindows server 2022 | stated at publication 10.0.20348.1726, now states 10.0.20348.3932Release 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 11 Feb 2025· 1 change | |||||
| 2025-02-11 | Fix version moved | CVE-2023-24932 | microsoftwindows 11 version 21h2 | stated at publication 10.0.22000.1936, now states 10.0.22000.3079Release 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 1 Jan 2025· 205 changes | |||||
| 2025-01-01 | Fix version moved | microsoftwindows 10 version 21h2 | stated at publication 10.0.19041.3693, now states 10.0.19043.3693Release branch starts at *.not counted: Product line renumbered | Duration unknown | |
| 2025-01-01 | same kind of change as the line above | 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 |
| 2025-01-01 | same kind of change as the line above | 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 |
| 2025-01-01 | same kind of change as the line above | 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 |
| 2025-01-01 | same kind of change as the line above | 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 |
| 2025-01-01 | same kind of change as the line above | 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 |
| 2025-01-01 | same kind of change as the line above | 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 |
| 2025-01-01 | same kind of change as the line above | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-36394 | 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 |
| 12 more rows in this change are not listed here. Open all 20 rows → | |||||
| 2025-01-01 | Fix version moved | microsoftwindows 10 version 21h2 | stated at publication 10.0.19041.3208, now states 10.0.19044.3208Release branch starts at *.not counted: Product line renumbered | Duration unknown | |
| 2025-01-01 | same kind of change as the line above | CVE-2023-21526 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-21756 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-32034 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-32035 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-32037 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-32038 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-32039 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-32040 | 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 |
| 70 more rows in this change are not listed here. Open all 78 rows → | |||||
| 2025-01-01 | Fix version moved | microsoftwindows 11 version 22h2 | stated at publication 10.0.22621.2275, now states 10.0.22621.2283Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2025-01-01 | same kind of change as the line above | CVE-2023-35355 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-36802 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-36803 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-36804 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-36805 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-38139 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-38141 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-38142 | 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 |
| 9 more rows in this change are not listed here. Open all 17 rows → | |||||
| 2025-01-01 | Fix version moved | microsoftwindows server 2022 | stated at publication 10.0.20348.1960, now states 10.0.20348.1970Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2025-01-01 | same kind of change as the line above | CVE-2023-35355 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-36801 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-36802 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-36803 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-36804 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-36805 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-38139 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-38140 | 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 |
| 11 more rows in this change are not listed here. Open all 19 rows → | |||||
| 2025-01-01 | Fix version moved | microsoftwindows 11 version 22h2 | stated at publication 10.0.22000.1702, now states 10.0.22621.1702Release branch starts at *.not counted: Product line renumbered | Duration unknown | |
| 2025-01-01 | same kind of change as the line above | CVE-2023-24899 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-24900 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-24901 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-24902 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-24903 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-24905 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-24939 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-24940 | 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 |
| 10 more rows in this change are not listed here. Open all 18 rows → | |||||
| 2025-01-01 | Fix version moved | microsoftwindows 11 version 22h2 | stated at publication 10.0.22000.1413, now states 10.0.22621.1413Release branch starts at *.not counted: Product line renumbered | Duration unknown | |
| 2025-01-01 | same kind of change as the line above | CVE-2023-21708 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-23385 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-23388 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-23392 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-23393 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-23394 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-23401 | 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 |
| 2025-01-01 | same kind of change as the line above | CVE-2023-23402 | 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 |
| 44 more rows in this change are not listed here. Open all 52 rows → | |||||
| 2025-01-01 | Fix version moved | CVE-2023-21712 | microsoftwindows 11 version 22h2 | stated at publication 10.0.22000.819, now states 10.0.22621.819Release branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Duration unknown |
| Tue 31 Dec 2024· 176 changes | |||||
| 2024-12-31 | Fix version moved | microsoftwindows 10 version 1507 | stated at publication 10.0.10240.20796, now states 10.0.10240.20826Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | Fix version moved | CVE-2024-43511 | microsoft3 products | stated at publication 10.0.14393.7428, now states 10.0.14393.7515Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43511 | 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 | Fix version moved | 7 rows, one per record and product | microsoft3 products | stated at publication 10.0.17763.6414, now states 10.0.17763.6532Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | same kind of change as the line above | CVE-2024-43528 | 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 | Fix version moved | microsoftwindows 10 version 21h2 | stated at publication 10.0.19044.5011, now states 10.0.19044.5131Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | Fix version moved | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.5011, now states 10.0.19045.5131Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | Fix version moved | microsoftwindows 11 version 22h2 | stated at publication 10.0.22621.4317, now states 10.0.22621.4460Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | Fix version moved | 4 rows, one per record and product | microsoft2 products | stated at publication 10.0.22631.4317, now states 10.0.22631.4460Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | Fix version moved | microsoftwindows 11 version 24h2 | stated at publication 10.0.26100.2033, now states 10.0.26100.2303Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | Fix version moved | microsoftwindows server 2022, 23h2 edition (server core installation) | stated at publication 10.0.25398.1189, now states 10.0.25398.1251Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | same kind of change as the line above | CVE-2024-43511 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | Fix version moved | CVE-2024-43516 | microsoft3 products | stated at publication 10.0.14393.7428, now states 10.0.14393.7515Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | same kind of change as the line above | CVE-2024-43516 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | same kind of change as the line above | CVE-2024-43516 | 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 | Fix version moved | CVE-2024-38063 | microsoft3 products | stated at publication 10.0.17763.6189, now states 10.0.17763.6293Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | same kind of change as the line above | CVE-2024-38063 | 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 | same kind of change as the line above | CVE-2024-38063 | 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 | same kind of change as the line above | CVE-2024-38063 | 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 | Fix version moved | microsoftwindows server 2022 | stated at publication 10.0.20348.2655, now states 10.0.20348.2700Release branch starts at *.not counted: Release branches rewritten | Duration unknown | |
| 2024-12-31 | same kind of change as the line above | CVE-2024-38063 | 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 | same kind of change as the line above | CVE-2024-38138 | 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 | Fix version moved | CVE-2024-38138 | microsoft2 products | stated at publication 10.0.14393.7259, now states 10.0.14393.7336Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | same kind of change as the line above | CVE-2024-38138 | 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 | same kind of change as the line above | CVE-2024-38138 | 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 | Fix version moved | CVE-2024-38138 | microsoft2 products | stated at publication 10.0.17763.6189, now states 10.0.17763.6414Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | same kind of change as the line above | CVE-2024-38138 | 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 | same kind of change as the line above | CVE-2024-38138 | 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 | Fix version moved | CVE-2024-38138 | microsoftwindows server 2022, 23h2 edition (server core installation) | stated at publication 10.0.25398.1085, now states 10.0.25398.1128Release 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 | Fix version moved | CVE-2024-38033 | microsoft2 products | stated at publication 6.2.9200.24975, now states 6.2.9200.25222Release branch starts at *.not counted: Release branches rewritten | Duration unknown |
| 2024-12-31 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 | Fix version moved | 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 | same kind of change as the line above | 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 | same kind of change as the line above | 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 |
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 →