Every change, newest first
One change, in full: Product added: 11 products named as affected from microsoft. The same change in 7 CVE records, across 11 products: 15 rows in all. Drawn here as 3 lines, one per product. 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 | Product added | CVE-2026-41100 | not named as affected at publication, now names microsoft excel for android and 4 more | Time to revision 28 days | |
| 2026-06-09 | same kind of change as the line above | CVE-2026-41100 | same vendor as the line above | not named as affected at publication, now names microsoft excel for android | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-41100 | same vendor as the line above | not named as affected at publication, now names microsoft loop for android | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-41100 | same vendor as the line above | not named as affected at publication, now names microsoft onenote for android | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-41100 | same vendor as the line above | not named as affected at publication, now names microsoft powerpoint for android | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-41100 | same vendor as the line above | not named as affected at publication, now names microsoft word for android | Time to revision 28 days |
| 2026-06-09 | Product added | not named as affected at publication, now names windows 11 version 26h1 | Time to revision 511 to 609 days | ||
| 2026-06-09 | same kind of change as the line above | CVE-2024-43582 | same vendor as the line above | same change as the line above | Time to revision 609 days |
| 2026-06-09 | same kind of change as the line above | CVE-2024-49075 | same vendor as the line above | same change as the line above | Time to revision 546 days |
| 2026-06-09 | same kind of change as the line above | CVE-2024-49123 | same vendor as the line above | same change as the line above | Time to revision 546 days |
| 2026-06-09 | same kind of change as the line above | CVE-2024-49132 | same vendor as the line above | same change as the line above | Time to revision 546 days |
| 2026-06-09 | same kind of change as the line above | CVE-2025-21330 | same vendor as the line above | same change as the line above | Time to revision 511 days |
| 2026-06-09 | Product added | CVE-2026-21530 | not named as affected at publication, now names microsoft 365 apps for enterprise and 4 more | Time to revision 28 days | |
| 2026-06-09 | same kind of change as the line above | CVE-2026-21530 | same vendor as the line above | not named as affected at publication, now names microsoft 365 apps for enterprise | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-21530 | same vendor as the line above | not named as affected at publication, now names microsoft office 2016 | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-21530 | same vendor as the line above | not named as affected at publication, now names microsoft office 2019 | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-21530 | same vendor as the line above | not named as affected at publication, now names microsoft office ltsc 2021 | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-21530 | same vendor as the line above | not named as affected at publication, now names microsoft office ltsc 2024 | 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. 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 →