Every change, newest first
Showing changes seen on 2026-08-12. Every day
These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.
| Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin. | Kind | Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on. | Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry. | What changed | Days to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong. |
|---|---|---|---|---|---|
| Wed 12 Aug 2026· 25 changes | |||||
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoft3 products | stated at publication 10.0.14393.9234, now states 10.0.14393.9418Release branch starts at 10.0.14393.0.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoftwindows 10 version 21h2 | stated at publication 10.0.19044.7417, now states 10.0.19044.7663Release branch starts at 10.0.19044.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7417, now states 10.0.19045.7663Release branch starts at 10.0.19045.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2704Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoft2 products | stated at publication 6.2.9200.26132, now states 6.2.9200.26280Release branch starts at 6.2.9200.0.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoft2 products | stated at publication 6.3.9600.23228, now states 6.3.9600.23338Release branch starts at 6.3.9600.0.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoft2 products | stated at publication 10.0.26100.32995, now states 10.0.26100.33296Release branch starts at 10.0.26100.0.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Product added | not named as affected at publication, now names red hat jboss enterprise application platform 7.4.25not counted: Added entry does not state affected status | Time to revision 1 days | ||
| 2026-08-12 | same kind of change as the line above | CVE-2026-15554 | same vendor as the line above | same change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15555 | same vendor as the line above | same change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15556 | same vendor as the line above | same change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15560 | same vendor as the line above | same change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15561 | same vendor as the line above | same change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15562 | same vendor as the line above | same change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15563 | same vendor as the line above | same change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15565 | same vendor as the line above | same change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure | Time to revision 1 days |
| 1 more row in this change is not listed here. Open all 9 rows → | |||||
| 2026-08-123 commits | Product added | CVE-2026-56208 | not named as affected at publication, now names red hat enterprise linux 9.6 extended update support and 3 moreBranches and original-value intervals are stated on each row.not counted: A variant beneath an already affected parent | Time to revision 54 days | |
| 2026-08-12 | same kind of change as the line above | CVE-2026-56208 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 9.6 extended update supportNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 9; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 54 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-56208 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 10.0 extended update supportNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 10; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 54 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-56208 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 9.4 update services for sap solutionsNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 9; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 54 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-56208 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 9.2 update services for sap solutionsNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 9; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 54 days |
Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
What this page cannot see
Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
The units, the refusals, the cut-offs and every source, in full →
Paste your closed CVE tickets and see which of these changes hit them →