Every change, newest first
These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.
| Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin. | Kind | Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on. | Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry. | What changed | Days to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong. |
|---|---|---|---|---|---|
| Tue 1 Sep 2026· 6 record changes | |||||
| 2026-09-01 | Forensic triage now required | CVE-2019-1068 | MicrosoftSQL Server CISA KEV | stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Days to revision 6 |
| 2026-09-01 | Forensic triage now required | MicrosoftSharePoint | stated at publication not stated, now states Yesnot counted: The prior instruction already required triage | Days to revision 14 to 47 | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-55040 | same vendor as the line above | same change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Days to revision 14 |
| 2026-09-01 | same kind of change as the line above | CVE-2026-50522 | same vendor as the line above | same change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Days to revision 41 |
| 2026-09-01 | same kind of change as the line above | CVE-2026-58644 | same vendor as the line above | same change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Days to revision 47 |
| 2026-09-01 | Forensic triage now required | MicrosoftSharePoint Server | stated at publication not stated, now states Yesnot counted: The prior instruction already required triage | Days to revision 49 to 62 | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-56164 | same vendor as the line above | same change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Days to revision 49 |
| 2026-09-01 | same kind of change as the line above | CVE-2026-45659 | same vendor as the line above | same change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Days to revision 62 |
| Fri 21 Aug 2026· 2 record changes | |||||
| 2026-08-21 | Fix version moved | CVE-2026-54981 | microsoftpython extension for visual studio code | stated at publication 1.132.1, now states 2026.3.1Release branch starts at 2020.Not counted: Version scheme changed. one side is on a calendar versioning scheme and the other is not — the two are not comparable in either direction | Days to revision 10 |
| 2026-08-21 | Removed from CISA KEV | CVE-2026-69836 | MicrosoftEntra ID CISA KEV | Previously listed from 2026-08-21Not counted: Same-day catalog correction. entry stood 1.2 hours before being withdrawn — a same-day catalog correction, not a KEV listing anyone escalated | Days to revision 0 |
| Tue 18 Aug 2026· 1 record change | |||||
| 2026-08-18 | Product added | CVE-2026-47632 | not named as affected at publication, now names azure connected machine agentNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed microsoft/azure monitor agent metrics extension; a new product identity is not established | Days to revision 35 | |
| Sun 16 Aug 2026· 6 record changes | |||||
| 2026-08-16 | Fix version moved | CVE-2026-42976 | microsoft3 products | stated at publication 10.0.17763.8880, now states 10.0.17763.9121Release branch starts at 10.0.17763.0.Original value first replaced 2026-08-12; this value first seen 2026-08-16.not counted: Build number corrected to the one that shipped | Days to revision 1 |
| 2026-08-16 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Original value first replaced 2026-08-12; this value first seen 2026-08-16.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 1 |
| 2026-08-16 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Original value first replaced 2026-08-12; this value first seen 2026-08-16.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 1 |
| 2026-08-16 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Original value first replaced 2026-08-12; this value first seen 2026-08-16.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 1 |
| 2026-08-16 | Fix version moved | CVE-2026-49179 | microsoft3 products | stated at publication 10.0.17763.9115, now states 10.0.17763.9121Release branch starts at 10.0.17763.0.not counted: Build number corrected to the one that shipped | Days to revision 5 |
| 2026-08-16 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 5 |
| 2026-08-16 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 5 |
| 2026-08-16 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 5 |
| Wed 12 Aug 2026· 12 record 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| Tue 11 Aug 2026· 4 record changes | |||||
| 2026-08-11 | Fix version moved | CVE-2026-49179 | microsoft2 products | stated at publication 6.2.9200.26279, now states 6.2.9200.26280Release branch starts at 6.2.9200.0.not counted: Build number corrected to the one that shipped | Days to revision 0 |
| 2026-08-11 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 0 |
| 2026-08-11 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 0 |
| 2026-08-11 | Fix version moved | CVE-2026-49179 | microsoft2 products | stated at publication 6.3.9600.23337, now states 6.3.9600.23338Release branch starts at 6.3.9600.0.not counted: Build number corrected to the one that shipped | Days to revision 0 |
| 2026-08-11 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 0 |
| 2026-08-11 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 0 |
Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. 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 →