Every fix version that moved
These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.
| Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin. | Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on. | Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry. | What changed | Days to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong. |
|---|---|---|---|---|
| Wed 1 Apr 2026· 5 changes | ||||
| 2026-04-01 | CVE-2026-35099 | lakeside softwaresystrack agent mitre | stated at publication 11.2.1.28, now states 11.5.0.15Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 11.2.1.28 still holds | Duration unknown |
| 2026-04-01 | CVE-2025-58214 | gaviasindutri Patchstack | stated at publication 1.3.0, now states 1.3.0Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 208 days |
| 2026-04-01 | CVE-2025-58215 | gaviasziston Patchstack | stated at publication 1.4.5, now states 1.4.5Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 204 days |
| 2026-04-01 | CVE-2025-58628 | kamleshyadavmiraculous Patchstack | stated at publication 2.0.9, now states 2.0.9Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 208 days |
| 2026-04-01 | CVE-2025-10450 | rticonnext professional | stated at publication 7.3.1, now states 7.7.0Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.3.1 still holds | Duration unknown |
| Thu 26 Mar 2026· 1 change | ||||
| 2026-03-26 | CVE-2025-9551 | drupalprotected pages | stated at publication 1.8.0, now states 7.x-2.5Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 1.8.0 still holds | Duration unknown |
| Wed 25 Mar 2026· 1 change | ||||
| 2026-03-25 | CVE-2026-20643 | applemacos | stated at publication 26.3.2 (a), now states 26.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 26.3.2 (a) still holds | Duration unknown |
| Thu 12 Mar 2026· 1 change | ||||
| 2026-03-12 | CVE-2024-23222 | appleios and ipados | stated at publication 16.7, now states 16.7.5Release branch starts at 0.Original value first replaced 2024-02-21; this value first seen 2026-03-12.Not counted: Description already named the later value. the record's own description at publication already named 16.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 29 days |
| Wed 4 Mar 2026· 2 changes | ||||
| 2026-03-04 | CVE-2026-3204 | devolutionsserver | stated at publication 2025.3.16, now states 2025.3.16Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 1 days |
| 2026-03-04 | CVE-2026-21425 | dellpowerscale onefs | stated at publication 9.10.1.6 or later, now states 9.13.0.0 or laterRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 9.10.1.6 or later still holds | Duration unknown |
| Wed 28 Jan 2026· 1 change | ||||
| 2026-01-28 | CVE-2025-47705 | drupaliframe remove filter | stated at publication 2.0.5, now states 7.x-1.5Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 2.0.5 still holds | Duration unknown |
| Fri 23 Jan 2026· 2 changes | ||||
| 2026-01-23 | 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 | 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 | 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· 12 changes | ||||
| 2026-01-202 commits | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | CVE-2025-3125 | wso24 products | stated at publication 4.5.0.2, now states 4.6.0.3Release branch starts at *.not counted: Another branch advanced | Duration unknown |
| 2026-01-20 | CVE-2025-3125 | 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 4.5.0.2 still holds | Duration unknown |
| 2026-01-20 | CVE-2025-3125 | 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 4.5.0.2 still holds | Duration unknown |
| 2026-01-20 | CVE-2025-3125 | 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 4.5.0.2 still holds | Duration unknown |
| 2026-01-20 | CVE-2025-3125 | 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 4.5.0.2 still holds | Duration unknown |
| Fri 19 Dec 2025· 1 change | ||||
| 2025-12-19 | CVE-2025-68161 | apache software foundationapache log4j core apache | stated at publication 2.25.3, now states 3.0.0-beta3Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 2.25.3 still holds | Duration unknown |
| Mon 15 Dec 2025· 1 change | ||||
| 2025-12-15 | CVE-2025-9624 | opensearchopensearch Fluid Attacks | stated at publication 3.2.0, now states 3.3.0Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 3.2.0 still holds | Duration unknown |
| Mon 1 Dec 2025· 1 change | ||||
| 2025-12-01 | CVE-2025-40084 | linuxlinux | stated at publication 6.17.6, now states 6.18Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.17.6 still holds | Duration unknown |
| Thu 6 Nov 2025· 1 change | ||||
| 2025-11-06 | CVE-2025-10280 | sailpoint technologiesidentityiq SailPoint | stated at publication 8.3p6, now states 8.3p5Release branch starts at 8.3.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 3 days |
| Wed 29 Oct 2025· 2 changes | ||||
| 2025-10-29 | newplaneopen5gs INCIBE | stated at publication 2.7.5, now states 2.7.5Release branch starts at 0.not counted: Same claim, other operator | Time to revision 2 days | |
| 2025-10-29 | CVE-2025-41067 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 2 days |
| 2025-10-29 | CVE-2025-41068 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 2 days |
| Fri 24 Oct 2025· 2 changes | ||||
| 2025-10-24 | CVE-2025-5350 | wso2org.wso2.carbon:org.wso2.carbon.ui | stated at publication 4.10.42.11, now states 4.10.93Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 4.10.42.11 still holds | Duration unknown |
| 2025-10-24 | CVE-2025-5605 | wso2org.wso2.carbon:org.wso2.carbon.ui | stated at publication 4.10.42.10, now states 4.10.90Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 4.10.42.10 still holds | Duration unknown |
| Thu 23 Oct 2025· 12 changes | ||||
| 2025-10-23 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
| Tue 21 Oct 2025· 1 change | ||||
| 2025-10-21 | CVE-2024-8008 | wso2wso2 api manager | stated at publication 4.3.0.32, now states 4.5.0.16Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 4.3.0.32 still holds | Duration unknown |
| Tue 14 Oct 2025· 16 changes | ||||
| 2025-10-14 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
| Sat 11 Oct 2025· 1 change | ||||
| 2025-10-11 | CVE-2025-40364 | linuxlinux | stated at publication 6.6.78, now states 6.14Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.6.78 still holds | Duration unknown |
| Fri 10 Oct 2025· 2 changes | ||||
| 2025-10-10 | CVE-2025-21988 | linuxlinux | stated at publication 6.13.8, now states 6.14Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.13.8 still holds | Duration unknown |
| 2025-10-10 | CVE-2023-53642 | linuxlinux | stated at publication 6.1.29, now states 6.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.1.29 still holds | Duration unknown |
| Mon 29 Sep 2025· 1 change | ||||
| 2025-09-29 | CVE-2025-40300 | linuxlinux | stated at publication 6.16.7, now states 6.17Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.16.7 still holds | Duration unknown |
| Tue 9 Sep 2025· 3 changes | ||||
| 2025-09-09 | 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 | 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 | 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 | 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 |
| Mon 1 Sep 2025· 1 change | ||||
| 2025-09-01 | CVE-2024-13987 | synologyradius server | stated at publication 3.0.27-0139, now states 3.0.27-0516Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 3.0.27-0139 still holds | Duration unknown |
| Wed 27 Aug 2025· 1 change | ||||
| 2025-08-27 | CVE-2025-41459 | two app studiojourney cirosec | stated at publication 5.5.9, now states 5.5.9Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 37 days |
| Sat 23 Aug 2025· 2 changes | ||||
| 2025-08-23 | 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 | 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 | 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 | 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 |
| Mon 28 Jul 2025· 1 change | ||||
| 2025-07-28 | CVE-2025-38001 | linuxlinux | stated at publication 6.15.1, now states 6.16Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.15.1 still holds | Duration unknown |
| Fri 18 Jul 2025· 1 change | ||||
| 2025-07-18 | 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 | 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 | 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 | 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 |
| Mon 14 Jul 2025· 8 changes | ||||
| 2025-07-14 | CVE-2024-4296 | hgigaisherlock 4.5 twcert | stated at publication 4.5-149, now states 149Release branch starts at earlier.Not counted: Version respelled. the same version rewritten — the range start or versionType was rewritten in the same change, or the dropped prefix is the product's own name | Time to revision 441 days |
| 2025-07-14 | CVE-2024-4296 | hgigaisherlock 5.5 twcert | stated at publication 5.5-149, now states 149Release branch starts at earlier.Not counted: Version respelled. the same version rewritten — the range start or versionType was rewritten in the same change, or the dropped prefix is the product's own name | Time to revision 441 days |
| 2025-07-14 | hgigaisherlock 4.5 twcert | stated at publication 4.5-147, now states 147Release branch starts at earlier.not counted: Version respelled | Time to revision 441 days | |
| 2025-07-14 | CVE-2024-4297 | same vendor as the line above | same change as the line aboveRelease branch starts at earlier.Not counted: Version respelled. the same version rewritten — the range start or versionType was rewritten in the same change, or the dropped prefix is the product's own name | Time to revision 441 days |
| 2025-07-14 | CVE-2024-4299 | same vendor as the line above | same change as the line aboveRelease branch starts at earlier.Not counted: Version respelled. the same version rewritten — the range start or versionType was rewritten in the same change, or the dropped prefix is the product's own name | Time to revision 441 days |
| 2025-07-14 | hgigaisherlock 5.5 twcert | stated at publication 5.5-147, now states 147Release branch starts at earlier.not counted: Version respelled | Time to revision 441 days | |
| 2025-07-14 | CVE-2024-4297 | same vendor as the line above | same change as the line aboveRelease branch starts at earlier.Not counted: Version respelled. the same version rewritten — the range start or versionType was rewritten in the same change, or the dropped prefix is the product's own name | Time to revision 441 days |
| 2025-07-14 | CVE-2024-4299 | same vendor as the line above | same change as the line aboveRelease branch starts at earlier.Not counted: Version respelled. the same version rewritten — the range start or versionType was rewritten in the same change, or the dropped prefix is the product's own name | Time to revision 441 days |
| 2025-07-14 | CVE-2024-4298 | hgigaisherlock 4.5 twcert | stated at publication 4.5-188, now states 188Release branch starts at earlier.Not counted: Version respelled. the same version rewritten — the range start or versionType was rewritten in the same change, or the dropped prefix is the product's own name | Time to revision 441 days |
| 2025-07-14 | CVE-2024-4298 | hgigaisherlock 5.5 twcert | stated at publication 5.5-188, now states 188Release branch starts at earlier.Not counted: Version respelled. the same version rewritten — the range start or versionType was rewritten in the same change, or the dropped prefix is the product's own name | Time to revision 441 days |
| Thu 10 Jul 2025· 10 changes | ||||
| 2025-07-10 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
| Mon 19 May 2025· 1 change | ||||
| 2025-05-19 | CVE-2025-36557 | f5big-ip | stated at publication 17.1.2, now states 17.5.0Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 17.1.2 still holds | Duration unknown |
| Fri 11 Apr 2025· 2 changes | ||||
| 2025-04-11 | CVE-2023-40425 | applemacos | stated at publication 12.7, now states 14Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 12.7 still holds | Duration unknown |
| 2025-04-11 | CVE-2023-41077 | applemacos | stated at publication 13.6, now states 14Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 13.6 still holds | Duration unknown |
| Thu 27 Mar 2025· 1 change | ||||
| 2025-03-27 | CVE-2025-2565 | liferaydxp | stated at publication 2024.Q1.13, now states 2024.Q1.12Release branch starts at 2024.Q1.1.Not counted: Same claim, other operator. `unaffected_start` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 7 days |
| Wed 12 Mar 2025· 2 changes | ||||
| 2025-03-12 | CVE-2025-1683 | 1e1e client | stated at publication 24.5, now states 24.5Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2025-03-12 | CVE-2025-1683 | 1e1e client | stated at publication 25.1, now states 25.1Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| Mon 10 Mar 2025· 1 change | ||||
| 2025-03-10 | CVE-2025-1015 | mozillathunderbird | stated at publication 128.7, now states 135Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 128.7 still holds | Duration unknown |
| Thu 20 Feb 2025· 1 change | ||||
| 2025-02-20 | CVE-2024-5921 | palo alto networksglobalprotect app palo_alto | stated at publication 6.2.6, now states 6.3.2Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.2.6 still holds | Duration unknown |
| Tue 11 Feb 2025· 1 change | ||||
| 2025-02-11 | 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 |
| Fri 3 Jan 2025· 1 change | ||||
| 2025-01-03 | CVE-2024-12801 | qos.ch sarllogback NCSC.ch | stated at publication 1.5.12, now states 1.5.12Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 15 days |
| Wed 1 Jan 2025· 205 changes | ||||
| 2025-01-01 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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· 41 changes | ||||
| 2024-12-31 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | CVE-2024-38033 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2024-12-31 | CVE-2024-38033 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
What this page cannot see
Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
The units, the refusals, the cut-offs and every source, in full →
Paste your closed CVE tickets and see which of these changes hit them →