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 changes | ||||
| 2026-09-03 | CVE-2026-13086 | watchguardfireware os | stated at publication 2026.2.2, now states 2026.3.1Release 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 | Duration unknown |
| 2026-09-03 | CVE-2026-19313 | watchguardfireware os | stated at publication 2026.2.2, now states 2026.3.1Release 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 | Duration unknown |
| 2026-09-03 | CVE-2026-19314 | watchguardfireware os | stated at publication 2026.2.2, now states 2026.3.1Release 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 | Duration unknown |
| 2026-09-03 | CVE-2026-19315 | watchguardfireware os | stated at publication 2026.2.2, now states 2026.3.1Release 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 | Duration unknown |
| 2026-09-03 | CVE-2026-19316 | watchguardfireware os | stated at publication 2026.2.2, now states 2026.3.1Release 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 | Duration unknown |
| 2026-09-03 | CVE-2026-19317 | watchguardfireware os | stated at publication 2026.2.2, now states 2026.3.1Release 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 | Duration unknown |
| 2026-09-03 | CVE-2026-19318 | watchguardfireware os | stated at publication 2026.2.2, now states 2026.3.1Release 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 | Duration unknown |
| Sat 29 Aug 2026· 28 changes | ||||
| 2026-08-29 | CVE-2026-14662 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14663 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14664 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14666 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14668 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14669 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14670 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14671 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14672 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14673 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14676 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14677 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14678 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14679 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14680 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-14681 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-15741 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-15742 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-16238 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-16239 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-16241 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-18024 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-18408 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-19385 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-6464 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-6469 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-6470 | 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. 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/ | Time to revision 16 days |
| 2026-08-29 | CVE-2026-6471 | 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. 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/ | Time to revision 16 days |
| Tue 25 Aug 2026· 4 changes | ||||
| 2026-08-25 | CVE-2026-28849 | applemacos | stated at publication 15.7.8, 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 15.7.8 still holds | Duration unknown |
| 2026-08-25 | CVE-2026-28900 | applemacos | stated at publication 15.7.8, 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 15.7.8 still holds | Duration unknown |
| 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 | Duration unknown |
| 2026-08-25 | CVE-2026-39877 | applemacos | stated at publication 15.7.8, 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 15.7.8 still holds | Duration unknown |
| Fri 21 Aug 2026· 5 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 | Time to revision 10 days |
| 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 | Time to revision 2 days |
| 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 | Duration unknown |
| 2026-08-21 | CVE-2026-28896 | applemacos | stated at publication 15.7.8, 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.8 still holds | Duration unknown |
| 2026-08-21 | CVE-2026-28926 | applemacos | stated at publication 15.7.8, 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.8 still holds | Duration unknown |
| Sun 16 Aug 2026· 6 changes | ||||
| 2026-08-16 | CVE-2026-42976 | microsoftwindows 10 version 1809 | 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. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-16 | CVE-2026-42976 | microsoftwindows server 2019 | 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. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-16 | CVE-2026-42976 | microsoftwindows server 2019 (server core installation) | 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. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-16 | CVE-2026-49179 | microsoftwindows 10 version 1809 | 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. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 5 days |
| 2026-08-16 | CVE-2026-49179 | microsoftwindows server 2019 | 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. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 5 days |
| 2026-08-16 | CVE-2026-49179 | microsoftwindows server 2019 (server core installation) | 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. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 5 days |
| Wed 12 Aug 2026· 12 changes | ||||
| 2026-08-12 | CVE-2026-42976 | microsoftwindows 10 version 1607 | 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. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | CVE-2026-42976 | microsoftwindows 10 version 21h2 | stated at publication 10.0.19044.7417, now states 10.0.19044.7663Release branch starts at 10.0.19044.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | CVE-2026-42976 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7417, now states 10.0.19045.7663Release branch starts at 10.0.19045.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | CVE-2026-42976 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2704Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | CVE-2026-42976 | microsoftwindows server 2012 | 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. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | CVE-2026-42976 | microsoftwindows server 2012 (server core installation) | 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. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | CVE-2026-42976 | microsoftwindows server 2012 r2 | 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. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | CVE-2026-42976 | microsoftwindows server 2012 r2 (server core installation) | 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. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | CVE-2026-42976 | microsoftwindows server 2016 | 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. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | CVE-2026-42976 | microsoftwindows server 2016 (server core installation) | 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. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | CVE-2026-42976 | microsoftwindows server 2025 | 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. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | CVE-2026-42976 | microsoftwindows server 2025 (server core installation) | 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. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| Tue 11 Aug 2026· 4 changes | ||||
| 2026-08-11 | CVE-2026-49179 | microsoftwindows server 2012 | 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. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 0 days |
| 2026-08-11 | CVE-2026-49179 | microsoftwindows server 2012 (server core installation) | 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. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 0 days |
| 2026-08-11 | CVE-2026-49179 | microsoftwindows server 2012 r2 | 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. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 0 days |
| 2026-08-11 | CVE-2026-49179 | microsoftwindows server 2012 r2 (server core installation) | 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. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 0 days |
| Mon 10 Aug 2026· 34 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 | Time to revision 5 days |
| 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 | Time to revision 152 days |
| 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 | Time to revision 152 days |
| 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 | Time to revision 152 days |
| 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 | Time to revision 153 days |
| 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 | Time to revision 52 days |
| 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 | Time to revision 54 days |
| 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 | Time to revision 58 days |
| 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 | Time to revision 58 days |
| 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 | Time to revision 58 days |
| 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 | Time to revision 58 days |
| 2026-08-10 | CVE-2026-6428 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 58 days |
| 2026-08-10 | CVE-2026-70369 | koha communitykoha TuranSec | stated at publication 24.11.17, now states 24.11.17Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70369 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70369 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70369 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70370 | koha communitykoha TuranSec | stated at publication 24.11.17, now states 24.11.17Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70370 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70370 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70370 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70371 | koha communitykoha TuranSec | stated at publication 24.11.17, now states 24.11.17Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70371 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70371 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70371 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70372 | koha communitykoha TuranSec | stated at publication 24.11.17, now states 24.11.17Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70372 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70372 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70372 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70373 | koha communitykoha TuranSec | stated at publication 24.11.17, now states 24.11.17Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70373 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70373 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | CVE-2026-70373 | 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. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 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 | Time to revision 5 days |
| 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 | Time to revision 5 days |
This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller.
What this page cannot see
Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
The units, the refusals, the cut-offs and every source, in full →
Paste your closed CVE tickets and see which of these changes hit them →