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. |
|---|---|---|---|---|
| Thu 3 Sep 2026· 7 record changes | ||||
| 2026-09-03 | watchguardfireware os | stated at publication 2026.2.2, now states 2026.3.1Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2026-09-03 | CVE-2026-13086 | 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 2026.2.2 still holds | not dated |
| 2026-09-03 | CVE-2026-19313 | 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 2026.2.2 still holds | not dated |
| 2026-09-03 | CVE-2026-19314 | 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 2026.2.2 still holds | not dated |
| 2026-09-03 | CVE-2026-19315 | 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 2026.2.2 still holds | not dated |
| 2026-09-03 | CVE-2026-19316 | 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 2026.2.2 still holds | not dated |
| 2026-09-03 | CVE-2026-19317 | 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 2026.2.2 still holds | not dated |
| 2026-09-03 | CVE-2026-19318 | 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 2026.2.2 still holds | not dated |
| Sat 29 Aug 2026· 28 record changes | ||||
| 2026-08-29 | vendor not namedpostgresql PostgreSQL | stated at publication 18.5, now states 18.6Release branch starts at 18.not counted: The earlier release did not ship | Days to revision 16 | |
| 2026-08-29 | CVE-2026-14662 | same vendor as the line above | same change as the line aboveRelease branch starts at 18.Not counted: The earlier release did not ship. the publisher states 18.5 was not shipped; this is a catalog correction to 18.6, not a superseded installed fix — https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/ | Days to revision 16 |
| 2026-08-29 | CVE-2026-14663 | same vendor as the line above | same change as the line aboveRelease branch starts at 18.Not counted: The earlier release did not ship. the publisher states 18.5 was not shipped; this is a catalog correction to 18.6, not a superseded installed fix — https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/ | Days to revision 16 |
| 2026-08-29 | CVE-2026-14664 | same vendor as the line above | same change as the line aboveRelease branch starts at 18.Not counted: The earlier release did not ship. the publisher states 18.5 was not shipped; this is a catalog correction to 18.6, not a superseded installed fix — https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/ | Days to revision 16 |
| 2026-08-29 | CVE-2026-14666 | same vendor as the line above | same change as the line aboveRelease branch starts at 18.Not counted: The earlier release did not ship. the publisher states 18.5 was not shipped; this is a catalog correction to 18.6, not a superseded installed fix — https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/ | Days to revision 16 |
| 2026-08-29 | CVE-2026-14668 | same vendor as the line above | same change as the line aboveRelease branch starts at 18.Not counted: The earlier release did not ship. the publisher states 18.5 was not shipped; this is a catalog correction to 18.6, not a superseded installed fix — https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/ | Days to revision 16 |
| 2026-08-29 | CVE-2026-14669 | same vendor as the line above | same change as the line aboveRelease branch starts at 18.Not counted: The earlier release did not ship. the publisher states 18.5 was not shipped; this is a catalog correction to 18.6, not a superseded installed fix — https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/ | Days to revision 16 |
| 2026-08-29 | CVE-2026-14670 | same vendor as the line above | same change as the line aboveRelease branch starts at 18.Not counted: The earlier release did not ship. the publisher states 18.5 was not shipped; this is a catalog correction to 18.6, not a superseded installed fix — https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/ | Days to revision 16 |
| 2026-08-29 | CVE-2026-14671 | same vendor as the line above | same change as the line aboveRelease branch starts at 18.Not counted: The earlier release did not ship. the publisher states 18.5 was not shipped; this is a catalog correction to 18.6, not a superseded installed fix — https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/ | Days to revision 16 |
| 20 more rows in this change are not listed here. Open all 28 rows → | ||||
| Tue 25 Aug 2026· 4 record changes | ||||
| 2026-08-25 | applemacos | stated at publication 15.7.8, now states 26.5Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2026-08-25 | CVE-2026-28849 | 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 15.7.8 still holds | not dated |
| 2026-08-25 | CVE-2026-28900 | 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 15.7.8 still holds | not dated |
| 2026-08-25 | CVE-2026-39877 | 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 15.7.8 still holds | not dated |
| 2026-08-25 | CVE-2026-28984 | appleios and ipados | stated at publication 18.7.10, now states 26.5Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 18.7.10 still holds | not dated |
| Fri 21 Aug 2026· 5 record changes | ||||
| 2026-08-21 | 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 | Days to revision 10 |
| 2026-08-21 | CVE-2026-63722 | icecodericecoder VulnCheck | stated at publication 8.1, now states 8.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 | Days to revision 2 |
| 2026-08-21 | CVE-2026-20672 | applemacos | stated at publication 15.7.8, now states 26.3Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 15.7.8 still holds | not dated |
| 2026-08-21 | applemacos | stated at publication 15.7.8, now states 26.4Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2026-08-21 | CVE-2026-28896 | 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 15.7.8 still holds | not dated |
| 2026-08-21 | CVE-2026-28926 | 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 15.7.8 still holds | not dated |
| Sun 16 Aug 2026· 6 record changes | ||||
| 2026-08-16 | 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 | Days to revision 1 |
| 2026-08-16 | 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 | Days to revision 1 |
| 2026-08-16 | 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 | Days to revision 1 |
| 2026-08-16 | 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 | Days to revision 1 |
| 2026-08-16 | 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 | Days to revision 5 |
| 2026-08-16 | 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 | Days to revision 5 |
| 2026-08-16 | 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 | Days to revision 5 |
| 2026-08-16 | 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 | Days to revision 5 |
| Wed 12 Aug 2026· 12 record changes | ||||
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| 2026-08-12 | 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 | Days to revision 1 |
| Tue 11 Aug 2026· 4 record changes | ||||
| 2026-08-11 | 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 | Days to revision 0 |
| 2026-08-11 | 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 | Days to revision 0 |
| 2026-08-11 | 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 | Days to revision 0 |
| 2026-08-11 | 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 | Days to revision 0 |
| 2026-08-11 | 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 | Days to revision 0 |
| 2026-08-11 | 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 | Days to revision 0 |
| Mon 10 Aug 2026· 52 record changes | ||||
| 2026-08-10 | CVE-2026-18933 | wp-downloadmanagerwp-downloadmanager TuranSec | stated at publication 1.69, now states 1.69Release 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 | Days to revision 5 |
| 2026-08-10 | CVE-2026-31844 | koha communitykoha TuranSec | stated at publication 24.11.12, now states 24.11.12Release branch starts at 24.11.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 | Days to revision 152 |
| 2026-08-10 | CVE-2026-31844 | koha communitykoha TuranSec | stated at publication 25.05.07, now states 25.05.07Release branch starts at 25.05.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 | Days to revision 152 |
| 2026-08-10 | CVE-2026-31844 | koha communitykoha TuranSec | stated at publication 25.11.01, now states 25.11.01Release branch starts at 25.11.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 | Days to revision 152 |
| 2026-08-10 | CVE-2026-3843 | nefteprodukttekhnika llcbuk ts-g gas station automation system TuranSec | stated at publication 2.10.2, now states 2.10.2Release branch starts at 2.9.1.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 153 |
| 2026-08-10 | CVE-2026-54414 | error311filerise TuranSec | stated at publication 3.16.0, now states 3.16.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 | Days to revision 52 |
| 2026-08-10 | CVE-2026-54415 | azuriomazuriom cms TuranSec | stated at publication 1.2.11, now states 1.2.11Release 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 | Days to revision 54 |
| 2026-08-10 | CVE-2026-6428 | koha communitykoha TuranSec | stated at publication 22.11.38, now states 22.11.38Release 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 | Days to revision 58 |
| 2026-08-10 | CVE-2026-6428 | koha communitykoha TuranSec | stated at publication 24.11.16, now states 24.11.16Release branch starts at 24.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 58 |
| 2026-08-10 | CVE-2026-6428 | koha communitykoha TuranSec | stated at publication 25.05.11, now states 25.05.11Release branch starts at 25.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 58 |
| 2026-08-10 | CVE-2026-6428 | koha communitykoha TuranSec | stated at publication 25.11.05, now states 25.11.05Release branch starts at 25.11.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 58 |
| 2026-08-10 | koha communitykoha TuranSec | stated at publication 26.05.01, now states 26.05.01Release branch starts at 26.05.00.not counted: Same claim, other operator | Days to revision 6 to 58 | |
| 2026-08-10 | CVE-2026-6428 | same vendor as the line above | same change as the line aboveRelease branch starts at 26.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 58 |
| 2026-08-10 | CVE-2026-70369 | same vendor as the line above | same change as the line aboveRelease branch starts at 26.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70370 | same vendor as the line above | same change as the line aboveRelease branch starts at 26.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70371 | same vendor as the line above | same change as the line aboveRelease branch starts at 26.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70372 | same vendor as the line above | same change as the line aboveRelease branch starts at 26.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70373 | same vendor as the line above | same change as the line aboveRelease branch starts at 26.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | koha communitykoha TuranSec | stated at publication 24.11.17, now states 24.11.17Release branch starts at 0.not counted: Same claim, other operator | Days to revision 6 | |
| 2026-08-10 | CVE-2026-70369 | 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 | Days to revision 6 |
| 2026-08-10 | CVE-2026-70370 | 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 | Days to revision 6 |
| 2026-08-10 | CVE-2026-70371 | 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 | Days to revision 6 |
| 2026-08-10 | CVE-2026-70372 | 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 | Days to revision 6 |
| 2026-08-10 | CVE-2026-70373 | 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 | Days to revision 6 |
| 2026-08-10 | koha communitykoha TuranSec | stated at publication 25.05.12, now states 25.05.12Release branch starts at 25.05.00.not counted: Same claim, other operator | Days to revision 6 | |
| 2026-08-10 | CVE-2026-70369 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70370 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70371 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70372 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70373 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | koha communitykoha TuranSec | stated at publication 25.11.06, now states 25.11.06Release branch starts at 25.11.00.not counted: Same claim, other operator | Days to revision 6 | |
| 2026-08-10 | CVE-2026-70369 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.11.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70370 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.11.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70371 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.11.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70372 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.11.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70373 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.11.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 6 |
| 2026-08-10 | CVE-2026-70376 | pluck-cmspluck cms TuranSec | stated at publication 4.7.21, now states 4.7.21Release 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 | Days to revision 5 |
| 2026-08-10 | CVE-2026-71232 | magicblackmaccms10 TuranSec | stated at publication 10, now states 10Release 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 | Days to revision 5 |
| 2026-08-10 | CVE-2026-72564 | fosrlpangolin TuranSec | stated at publication 1.20.0, now states 1.20.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 | Days to revision 0 |
| 2026-08-10 | cube-rootdirectory-serve TuranSec | stated at publication 1.3.7, now states 1.3.7Release branch starts at 0.not counted: Same claim, other operator | Days to revision 0 | |
| 2026-08-10 | CVE-2026-72569 | 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72570 | 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72574 | picocmspico TuranSec | stated at publication 2.1.4, now states 2.1.4Release 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72575 | daptindaptin TuranSec | stated at publication v0.12.34, now states v0.12.34Release 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72577 | nasafprime-gds TuranSec | stated at publication 3.4.3, now states 3.4.3Release 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 | Days to revision 0 |
| 2026-08-10 | fastschemafastschema TuranSec | stated at publication 0.15.1, now states 0.15.1Release branch starts at 0.not counted: Same claim, other operator | Days to revision 0 | |
| 2026-08-10 | CVE-2026-72582 | 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72583 | 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72584 | 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72586 | frangoteamfuxa TuranSec | stated at publication 1.3.3, now states 1.3.3Release 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72587 | corebunchinstatic TuranSec | stated at publication 0.0.14, now states 0.0.14Release 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72588 | bluewave-labscheckmate TuranSec | stated at publication 2.1.0, now states 2.1.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 | Days to revision 0 |
| 2026-08-10 | alseambushercrontab-ui TuranSec | stated at publication 0.4.2, now states 0.4.2Release branch starts at 0.not counted: Same claim, other operator | Days to revision 0 | |
| 2026-08-10 | CVE-2026-72589 | 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72590 | 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72591 | gabehfkoito TuranSec | stated at publication 0.3.2, now states 0.3.2Release 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 | Days to revision 0 |
| 2026-08-10 | dullduskphpfm TuranSec | stated at publication 1.8.0, now states 1.8.0Release branch starts at 0.not counted: Same claim, other operator | Days to revision 0 | |
| 2026-08-10 | CVE-2026-72592 | 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72593 | 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 | Days to revision 0 |
| 2026-08-10 | CVE-2026-72594 | lobehublobe-chat TuranSec | stated at publication 2.2.13, now states 2.2.13Release 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 | Days to revision 0 |
| Fri 31 Jul 2026· 4 record changes | ||||
| 2026-07-31 | CVE-2026-10031 | drakkansftpgo VulnCheck | stated at publication 2.7.4, now states 2.7.4Release 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 | Days to revision 1 |
| 2026-07-31 | leantimeleantime VulnCheck | stated at publication 3.6.2, now states 3.6.2Release branch starts at 0.not counted: Same claim, other operator | Days to revision 1 | |
| 2026-07-31 | CVE-2026-66414 | 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 | Days to revision 1 |
| 2026-07-31 | CVE-2026-66415 | 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 | Days to revision 1 |
| 2026-07-31 | CVE-2026-66416 | 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 | Days to revision 1 |
| Wed 22 Jul 2026· 191 record changes | ||||
| 2026-07-22 | 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 | Days to revision 8 | |
| 2026-07-22 | 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 | Days to revision 8 |
| 2026-07-22 | 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 | Days to revision 8 |
| 2026-07-22 | 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 | Days to revision 8 |
| 2026-07-22 | 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 | Days to revision 8 |
| 2026-07-22 | 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 | Days to revision 8 |
| 2026-07-22 | 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 | Days to revision 8 |
| 2026-07-22 | 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 | Days to revision 8 |
| 2026-07-22 | 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 | Days to revision 8 |
| 183 more rows in this change are not listed here. Open all 191 rows → | ||||
| Tue 21 Jul 2026· 1 record change | ||||
| 2026-07-21 | CVE-2026-1995 | idriveidrive cloud backup client for windows certcc | stated at publication 7.0.0.63, now states 7.0.0.63Release 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 | Days to revision 119 |
| Mon 20 Jul 2026· 1 record change | ||||
| 2026-07-20 | CVE-2024-58362 | surrealdbsurrealdb VulnCheck | stated at publication 1.5.2, now states 2.0.0-beta.3Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 1.5.2 still holds | not dated |
| Tue 14 Jul 2026· 54 record changes | ||||
| 2026-07-14 | 54 rows, one per record, product and release branch | siemens18 products | stated at publication V2.9.9, now states V4.1.6Release branch starts at *.not counted: Another branch advanced | not dated |
| 2026-07-14 | CVE-2026-25786 | 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 V2.9.9 still holds | not dated |
| 2026-07-14 | CVE-2026-25786 | 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 V2.9.9 still holds | not dated |
| 2026-07-14 | CVE-2026-25786 | 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 V2.9.9 still holds | not dated |
| 2026-07-14 | CVE-2026-25786 | 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 V2.9.9 still holds | not dated |
| 2026-07-14 | CVE-2026-25786 | 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 V2.9.9 still holds | not dated |
| 2026-07-14 | CVE-2026-25786 | 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 V2.9.9 still holds | not dated |
| 2026-07-14 | CVE-2026-25786 | 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 V2.9.9 still holds | not dated |
| 2026-07-14 | CVE-2026-25786 | 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 V2.9.9 still holds | not dated |
| 46 more rows in this change are not listed here. Open all 54 rows → | ||||
| Fri 3 Jul 2026· 198 record changes | ||||
| 2026-07-032 commits | 198 rows, one per record, product and release branch | mbs18 products CERTVDE | stated at publication V6_0_0_7, now states V6_00_07Branches and original-value intervals are stated on each row.not counted: Version respelled | Days to revision 30 |
| 2026-07-03 | CVE-2026-35076 | same vendor as the line above | same change as the line aboveRelease branch starts at V1_0_0_0.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 | Days to revision 30 |
| 2026-07-03 | CVE-2026-35076 | same vendor as the line above | same change as the line aboveRelease branch starts at V1_0_0_0.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 | Days to revision 30 |
| 2026-07-03 | CVE-2026-35076 | same vendor as the line above | same change as the line aboveRelease branch starts at V1_0_0_0.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 | Days to revision 30 |
| 2026-07-03 | CVE-2026-35076 | same vendor as the line above | same change as the line aboveRelease branch starts at V1_0_0_0.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 | Days to revision 30 |
| 2026-07-03 | CVE-2026-35076 | same vendor as the line above | same change as the line aboveRelease branch starts at V1_0_0_0.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 | Days to revision 30 |
| 2026-07-03 | CVE-2026-35076 | same vendor as the line above | same change as the line aboveRelease branch starts at V1_0_0_0.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 | Days to revision 30 |
| 2026-07-03 | CVE-2026-35076 | same vendor as the line above | same change as the line aboveRelease branch starts at V1_0_0_0.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 | Days to revision 30 |
| 2026-07-03 | CVE-2026-35076 | same vendor as the line above | same change as the line aboveRelease branch starts at V1_0_0_0.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 | Days to revision 30 |
| 190 more rows in this change are not listed here. Open all 198 rows → | ||||
| Thu 18 Jun 2026· 1 record change | ||||
| 2026-06-18 | CVE-2025-13590 | wso2org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.impl | stated at publication 9.32.147.2, now states 9.32.167Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 9.32.147.2 still holds | not dated |
| Sun 14 Jun 2026· 59 record changes | ||||
| 2026-06-14 | linuxlinux | stated at publication 7.0.1, now states 7.1Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2026-06-14 | CVE-2026-31532 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | not dated |
| 2026-06-14 | CVE-2026-31574 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | not dated |
| 2026-06-14 | CVE-2026-31575 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | not dated |
| 2026-06-14 | CVE-2026-31576 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | not dated |
| 2026-06-14 | CVE-2026-31577 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | not dated |
| 2026-06-14 | CVE-2026-31578 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | not dated |
| 2026-06-14 | CVE-2026-31579 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | not dated |
| 2026-06-14 | CVE-2026-31580 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | not dated |
| 49 more rows in this change are not listed here. Open all 57 rows → | ||||
| 2026-06-14 | linuxlinux | stated at publication 7.0.3, now states 7.1Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2026-06-14 | CVE-2026-31786 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.3 still holds | not dated |
| 2026-06-14 | CVE-2026-31787 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.3 still holds | not dated |
| Wed 10 Jun 2026· 2 record changes | ||||
| 2026-06-10 | CVE-2025-71319 | image-sizeimage-size VulnCheck | stated at publication 1.2.1, now states 1.2.1Release branch starts at 1.1.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 | Days to revision 1 |
| 2026-06-10 | CVE-2025-71319 | image-sizeimage-size VulnCheck | stated at publication 2.0.2, now states 2.0.2Release branch starts at 2.0.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 | Days to revision 1 |
| Tue 9 Jun 2026· 37 record changes | ||||
| 2026-06-09 | 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 | not dated | |
| 2026-06-09 | 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 | not dated |
| 2026-06-09 | 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 | not dated |
| 2026-06-09 | 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 | not dated |
| 2026-06-09 | 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 | not dated |
| 2026-06-09 | 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 | not dated |
| 2026-06-09 | 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 | not dated |
| 2026-06-09 | 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 | not dated |
| 2026-06-09 | 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 | not dated |
| 29 more rows in this change are not listed here. Open all 37 rows → | ||||
| Wed 3 Jun 2026· 2 record changes | ||||
| 2026-06-03 | CVE-2024-14036 | drägercore VulnCheck | stated at publication 1.0.5, now states 1.0.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 | Days to revision 1 |
| 2026-06-03 | CVE-2024-14036 | drägerm540 converter service VulnCheck | stated at publication 1.0.9, now states 1.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 | Days to revision 1 |
| Mon 25 May 2026· 4 record changes | ||||
| 2026-05-25 | d-linknuclias connect VulnCheck | stated at publication 1.3.1.4, now states 1.3.1.4Release branch starts at 0.not counted: Same claim, other operator | Days to revision 221 | |
| 2026-05-25 | CVE-2025-34254 | 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 | Days to revision 221 |
| 2026-05-25 | CVE-2025-34255 | 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 | Days to revision 221 |
| 2026-05-25 | CVE-2026-25068 | alsa projectalsa-lib VulnCheck | stated at publication 1.2.15.2, now states 1.2.15.2Release branch starts at 1.2.2.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 116 |
| 2026-05-25 | CVE-2026-44400 | mailenablemailenable enterprise premium VulnCheck | stated at publication 10.55, now states 10.55Release 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 | Days to revision 17 |
| Fri 22 May 2026· 1 record change | ||||
| 2026-05-22 | 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 | Days to revision 6 |
| Mon 11 May 2026· 3 record changes | ||||
| 2026-05-11 | CVE-2026-29201 | webproswp squared hackerone | stated at publication 11.136.1.10, now states 11.136.1.11Release branch starts at 11.136.1.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 3.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 3 |
| 2026-05-11 | CVE-2026-20657 | appleios and ipados | stated at publication 18.7.7, 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 18.7.7 still holds | not dated |
| 2026-05-11 | CVE-2026-20657 | applemacos | stated at publication 15.7.5, 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 15.7.5 still holds | not dated |
| Mon 27 Apr 2026· 1 record change | ||||
| 2026-04-27 | CVE-2026-41080 | libexpat projectlibexpat mitre | stated at publication 2.7.6, now states 2.8.0Release branch starts at 0.Not counted: The earlier release did not ship. the publisher states 2.7.6 was not shipped; this is a catalog correction to 2.8.0, not a superseded installed fix — https://api.github.com/repos/libexpat/libexpat/tags?per_page=100 | Days to revision 11 |
| Thu 16 Apr 2026· 3 record changes | ||||
| 2026-04-16 | 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 | Days to revision 0 |
| 2026-04-16 | CVE-2026-39922 | geonodegeonode VulnCheck | stated at publication 4.4.5, now states 4.4.5Release branch starts at 4.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 | Days to revision 5 |
| 2026-04-16 | CVE-2026-39922 | geonodegeonode VulnCheck | stated at publication 5.0.2, now states 5.0.2Release branch starts at 5.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 | Days to revision 5 |
| Mon 13 Apr 2026· 21 record changes | ||||
| 2026-04-13 | linuxlinux | stated at publication 6.19.1, now states 7.0Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2026-04-13 | CVE-2025-71229 | 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 6.19.1 still holds | not dated |
| 2026-04-13 | CVE-2025-71230 | 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 6.19.1 still holds | not dated |
| 2026-04-13 | CVE-2025-71231 | 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 6.19.1 still holds | not dated |
| 2026-04-13 | CVE-2025-71232 | 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 6.19.1 still holds | not dated |
| 2026-04-13 | CVE-2025-71233 | 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 6.19.1 still holds | not dated |
| 2026-04-13 | CVE-2025-71234 | 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 6.19.1 still holds | not dated |
| 2026-04-13 | CVE-2025-71235 | 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 6.19.1 still holds | not dated |
| 2026-04-13 | CVE-2025-71236 | 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 6.19.1 still holds | not dated |
| 12 more rows in this change are not listed here. Open all 20 rows → | ||||
| 2026-04-13 | CVE-2026-31788 | linuxlinux | stated at publication 6.19.10, now states 7.0Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.19.10 still holds | not dated |
| Thu 2 Apr 2026· 230 record changes | ||||
| 2026-04-02 | applemacos | stated at publication 12.7, now states 12.7.4Release branch starts at 0.not counted: Description already named the later value | Days to revision 661 to 756 | |
| 2026-04-02 | CVE-2024-23201 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23216 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23227 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23230 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23234 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23244 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23245 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23247 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 15 more rows in this change are not listed here. Open all 23 rows → | ||||
| 2026-04-02 | applemacos | stated at publication 13.6, now states 13.6.5Release branch starts at 0.not counted: Description already named the later value | Days to revision 661 to 756 | |
| 2026-04-02 | CVE-2024-23201 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23216 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23227 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23229 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 689 |
| 2026-04-02 | CVE-2024-23230 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23231 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23234 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23245 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 17 more rows in this change are not listed here. Open all 25 rows → | ||||
| 2026-04-02 | appleios and ipados | stated at publication 16.7, now states 16.7.5Release branch starts at 0.not counted: Description already named the later value | Days to revision 708 to 801 | |
| 2026-04-02 | CVE-2024-23206 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 801 |
| 2026-04-02 | CVE-2024-23211 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 801 |
| 2026-04-02 | CVE-2024-23212 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 801 |
| 2026-04-02 | CVE-2024-23213 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 801 |
| 2026-04-02 | CVE-2024-23214 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 801 |
| 2026-04-02 | CVE-2024-27791 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 708 |
| 2026-04-02 | applemacos | stated at publication 12.7, now states 12.7.3Branches and original-value intervals are stated on each row.not counted: Description already named the later value | Days to revision 29 to 801 | |
| 2026-04-02 | CVE-2024-23207 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 801 |
| 2026-04-02 | CVE-2024-23212 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 801 |
| 2026-04-02 | CVE-2024-23222 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Original value first replaced 2024-02-21; this value first seen 2026-04-02.Not counted: Description already named the later value. the record's own description at publication already named 12.7.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 29 |
| 2026-04-02 | CVE-2024-27791 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 708 |
| 2026-04-02 | applemacos | stated at publication 13.6, now states 13.6.4Branches and original-value intervals are stated on each row.not counted: Description already named the later value | Days to revision 29 to 801 | |
| 2026-04-02 | CVE-2024-23207 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 801 |
| 2026-04-02 | CVE-2024-23212 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 801 |
| 2026-04-02 | CVE-2024-23222 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Original value first replaced 2024-02-21; this value first seen 2026-04-02.Not counted: Description already named the later value. the record's own description at publication already named 13.6.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 29 |
| 2026-04-02 | CVE-2024-23224 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 801 |
| 2026-04-02 | CVE-2024-27791 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.4 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 708 |
| 2026-04-02 | appleios and ipados | stated at publication 16.7, now states 16.7.6Release branch starts at 0.not counted: Description already named the later value | Days to revision 756 to 758 | |
| 2026-04-02 | CVE-2024-23225 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 758 |
| 2026-04-02 | CVE-2024-23231 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23235 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23246 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23257 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23259 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23262 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 2026-04-02 | CVE-2024-23263 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 756 |
| 7 more rows in this change are not listed here. Open all 15 rows → | ||||
| 2026-04-02 | applemacos | stated at publication 12.7, now states 12.7.5Release branch starts at 0.not counted: Description already named the later value | Days to revision 442 to 689 | |
| 2026-04-02 | CVE-2024-23229 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 689 |
| 2026-04-02 | CVE-2024-27789 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 689 |
| 2026-04-02 | CVE-2024-27799 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27800 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27802 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27805 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27806 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27817 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 5 more rows in this change are not listed here. Open all 13 rows → | ||||
| 2026-04-02 | appleios and ipados | stated at publication 16.7, now states 16.7.8Release branch starts at 0.not counted: Description already named the later value | Days to revision 442 to 689 | |
| 2026-04-02 | CVE-2024-23251 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-23282 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27789 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 689 |
| 2026-04-02 | CVE-2024-27799 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27800 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27802 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27805 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27806 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 11 more rows in this change are not listed here. Open all 19 rows → | ||||
| 2026-04-02 | applemacos | stated at publication 12.7, now states 12.7.6Release branch starts at 0.not counted: Description already named the later value | Days to revision 612 | |
| 2026-04-02 | CVE-2024-23261 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-27826 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-27873 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-27877 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-27881 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-27882 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-27883 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-40774 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.7.6 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 25 more rows in this change are not listed here. Open all 33 rows → | ||||
| 2026-04-02 | applemacos | stated at publication 13.6, now states 13.6.8Release branch starts at 0.not counted: Description already named the later value | Days to revision 612 | |
| 2026-04-02 | CVE-2024-23261 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-27826 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-27873 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-27877 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-27881 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-27882 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-27883 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-40774 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.8 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 29 more rows in this change are not listed here. Open all 37 rows → | ||||
| 2026-04-02 | CVE-2024-23300 | applegarageband | stated at publication 10.4, now states 10.4.11Release branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 10.4.11 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 751 |
| 2026-04-02 | applemacos | stated at publication 13.6, now states 13.6.7Release branch starts at 0.not counted: Description already named the later value | Days to revision 442 to 689 | |
| 2026-04-02 | CVE-2024-27789 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.7 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 689 |
| 2026-04-02 | CVE-2024-27799 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.7 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27800 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.7 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27802 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.7 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27805 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.7 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27806 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.7 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27817 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.7 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 661 |
| 2026-04-02 | CVE-2024-27823 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.6.7 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 5 more rows in this change are not listed here. Open all 13 rows → | ||||
| 2026-04-02 | CVE-2024-27793 | appleitunes for windows | stated at publication 12.13, now states 12.13.2Release branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 12.13.2 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 694 |
| 2026-04-02 | appleios and ipados | stated at publication 16.7, now states 16.7.9Release branch starts at 0.not counted: Description already named the later value | Days to revision 612 | |
| 2026-04-02 | CVE-2024-27873 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.9 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-40776 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.9 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-40778 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.9 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-40779 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.9 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-40780 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.9 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-40782 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.9 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-40784 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.9 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 2026-04-02 | CVE-2024-40785 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.7.9 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 612 |
| 15 more rows in this change are not listed here. Open all 23 rows → | ||||
| 2026-04-02 | appleios and ipados | stated at publication 18.3, now states 18.4Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2026-04-02 | CVE-2025-24113 | 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 18.3 still holds | not dated |
| 2026-04-02 | CVE-2025-24163 | 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 18.3 still holds | not dated |
| 2026-04-02 | CVE-2025-24113 | applemacos | stated at publication 15.3, now states 15.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 15.3 still holds | not dated |
| 2026-04-02 | CVE-2025-24113 | applesafari | stated at publication 18.3, now states 18.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 18.3 still holds | not dated |
| 2026-04-02 | applevisionos | stated at publication 2.3, now states 2.4Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2026-04-02 | CVE-2025-24113 | 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 2.3 still holds | not dated |
| 2026-04-02 | CVE-2025-24163 | 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 2.3 still holds | not dated |
| 2026-04-02 | CVE-2025-24163 | appletvos | stated at publication 18.3, now states 18.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 18.3 still holds | not dated |
| 2026-04-02 | CVE-2025-24163 | applewatchos | stated at publication 11.3, now states 11.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 11.3 still holds | not dated |
| 2026-04-02 | CVE-2025-31259 | applemacos | stated at publication 15.5, now states 26Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 15.5 still holds | not dated |
| 2026-04-02 | applemacos | stated at publication 15.7, now states 26Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2026-04-02 | CVE-2025-43288 | 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 15.7 still holds | not dated |
| 2026-04-02 | CVE-2025-43345 | 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 15.7 still holds | not dated |
| 2026-04-02 | CVE-2025-43364 | applemacos | stated at publication 15.7, now states 26.1Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 15.7 still holds | not dated |
This kind is counted once per record, product and release branch, so one record that moved the boundary on four branches counts four times and the number of records behind these changes is smaller. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
Data sources and quality
Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
The units, the refusals, the cut-offs and every source, in full →