Every change, newest first
One change, in full: Fix version moved: 10.0.19045.7291 → 10.0.19045.7417 from microsoft. The same change in 53 CVE records. Back to the ledger
| 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. |
|---|---|---|---|---|---|
| 2026-06-09 | Fix version moved | CVE-2026-21530 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-33834 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-33839 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-33841 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34329 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34330 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34331 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34333 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34342 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34343 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34344 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34345 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34347 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34351 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-35415 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-35416 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-35417 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-35418 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-35421 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-35422 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-35423 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-35424 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40377 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40380 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40399 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40406 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40407 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40408 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40410 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40414 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40415 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-41088 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-32161 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-32170 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-42825 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-33835 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-33837 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-33838 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34334 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34336 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34337 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34338 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34339 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34340 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-34341 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40382 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40397 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-32209 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40398 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40401 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40403 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-40413 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | Fix version moved | CVE-2026-41097 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.
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 →