Every change, newest first
One change, in full: Product added: 51 products named as affected in CVE-2026-35159. Products named as affected in 1 CVE record, across 51 products: 51 rows in all, one per record and 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-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 3650 mt | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 3660 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 3680 tower | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 5470 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 5480 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 5490 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 5560 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 5570 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 5680 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 5690 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 5770 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 5860 tower | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 7560 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 7670 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 7680 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 7760 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 7770 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 7780 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 7875 tower | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision 7960 tower | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names precision tower 7865 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 14 3420 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 14 3430 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 14 3440 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 15 3510 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 15 3520 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 15 3530 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 16 5630 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 16 5640 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 3020 small desktop | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 3020 tower desktop | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 3030 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 3030s | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 3910 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 5620 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 5890 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names vostro 7620 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 13 9315 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 13 9340 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 13 9350 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 13 plus 9320 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 14 (14 premium) da14250 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 14 9440 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 15 9510 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 15 9520 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 15 9530 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 16 (16 premium) da16250 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 16 9640 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 17 9720 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 17 9730 | Days to revision 0 | |
| 2026-07-03 | Product added | CVE-2026-35159 | not named as affected at publication, now names xps 9320 | 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.
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 →