Every change, newest first
| 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. |
|---|---|---|---|---|---|
| Sun 23 Nov 2025· 3 changes | |||||
| 2025-11-23 | Product added | CVE-2025-62626 | not named as affected at publication, now names amd epyc™ 9005 series processors | Time to revision 2 days | |
| 2025-11-23 | Product added | CVE-2023-20599 | not named as affected at publication, now names amd athlon™ 3000 series mobile processors with radeon™ graphics and 1 more | Time to revision 166 days | |
| 2025-11-23 | same kind of change as the line above | CVE-2023-20599 | same vendor as the line above | not named as affected at publication, now names amd athlon™ 3000 series mobile processors with radeon™ graphics | Time to revision 166 days |
| 2025-11-23 | same kind of change as the line above | CVE-2023-20599 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded v1000 series processors | Time to revision 166 days |
| Fri 21 Nov 2025· 2 changes | |||||
| 2025-11-21 | Product added | CVE-2023-20599 | not named as affected at publication, now names amd ryzen™ embedded r1000 series processors and 1 more | Time to revision 164 days | |
| 2025-11-21 | same kind of change as the line above | CVE-2023-20599 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded r1000 series processors | Time to revision 164 days |
| 2025-11-21 | same kind of change as the line above | CVE-2023-20599 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded r2000 series processors | Time to revision 164 days |
| Thu 25 Sep 2025· 29 changes | |||||
| 2025-09-25 | Product added | CVE-2024-36353 | not named as affected at publication, now names amd athlon™ 3000 series mobile processors with radeon™ graphics and 28 more | Time to revision 207 days | |
| 2025-09-25 | same kind of change as the line above | CVE-2024-36353 | same vendor as the line above | not named as affected at publication, now names amd athlon™ 3000 series mobile processors with radeon™ graphics | Time to revision 207 days |
| 2025-09-25 | same kind of change as the line above | CVE-2024-36353 | same vendor as the line above | not named as affected at publication, now names amd radeon™ pro v520 | Time to revision 207 days |
| 2025-09-25 | same kind of change as the line above | CVE-2024-36353 | same vendor as the line above | not named as affected at publication, now names amd radeon™ pro v620 | Time to revision 207 days |
| 2025-09-25 | same kind of change as the line above | CVE-2024-36353 | same vendor as the line above | not named as affected at publication, now names amd radeon™ pro v710 | Time to revision 207 days |
| 2025-09-25 | same kind of change as the line above | CVE-2024-36353 | same vendor as the line above | not named as affected at publication, now names amd radeon™ rx 5000/pro w5000 series graphics products | Time to revision 207 days |
| 2025-09-25 | same kind of change as the line above | CVE-2024-36353 | same vendor as the line above | not named as affected at publication, now names amd radeon™ rx 7000/pro w7000 series graphics products | Time to revision 207 days |
| 2025-09-25 | same kind of change as the line above | CVE-2024-36353 | same vendor as the line above | not named as affected at publication, now names amd radeon™ rx6000/pro w6000 series graphics products | Time to revision 207 days |
| 2025-09-25 | same kind of change as the line above | CVE-2024-36353 | same vendor as the line above | not named as affected at publication, now names amd ryzen embedded v2000a series processors | Time to revision 207 days |
| 21 more rows in this change are not listed here. Open all 29 rows → | |||||
| Mon 30 Jun 2025· 8 changes | |||||
| 2025-06-30 | Product added | CVE-2025-0036 | not named as affected at publication, now names alveo v80 compute accelerator and 7 more | Time to revision 21 days | |
| 2025-06-30 | same kind of change as the line above | CVE-2025-0036 | same vendor as the line above | not named as affected at publication, now names alveo v80 compute accelerator | Time to revision 21 days |
| 2025-06-30 | same kind of change as the line above | CVE-2025-0036 | same vendor as the line above | not named as affected at publication, now names versal adaptive soc devices | Time to revision 21 days |
| 2025-06-30 | same kind of change as the line above | CVE-2025-0036 | same vendor as the line above | not named as affected at publication, now names versal ai core series | Time to revision 21 days |
| 2025-06-30 | same kind of change as the line above | CVE-2025-0036 | same vendor as the line above | not named as affected at publication, now names versal ai edge series | Time to revision 21 days |
| 2025-06-30 | same kind of change as the line above | CVE-2025-0036 | same vendor as the line above | not named as affected at publication, now names versal hbm series | Time to revision 21 days |
| 2025-06-30 | same kind of change as the line above | CVE-2025-0036 | same vendor as the line above | not named as affected at publication, now names versal premium series | Time to revision 21 days |
| 2025-06-30 | same kind of change as the line above | CVE-2025-0036 | same vendor as the line above | not named as affected at publication, now names versal prime series | Time to revision 21 days |
| 2025-06-30 | same kind of change as the line above | CVE-2025-0036 | same vendor as the line above | not named as affected at publication, now names versal rf series | Time to revision 21 days |
| Fri 27 Jun 2025· 14 changes | |||||
| 2025-06-273 commits | Product added | 14 rows, one per record and product | not named as affected at publication, now names amd ryzen™ embedded 5000 and 8 moreBranches and original-value intervals are stated on each row. | Time to revision 136 to 646 days | |
| 2025-06-27 | same kind of change as the line above | CVE-2024-0179 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded 5000 | Time to revision 136 days |
| 2025-06-27 | same kind of change as the line above | CVE-2024-0179 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded 7000 | Time to revision 136 days |
| 2025-06-27 | same kind of change as the line above | CVE-2024-0179 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded r1000 | Time to revision 136 days |
| 2025-06-27 | same kind of change as the line above | CVE-2024-0179 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded v1000 | Time to revision 136 days |
| 2025-06-27 | same kind of change as the line above | CVE-2024-0179 | same vendor as the line above | not named as affected at publication, now names amd ryzen™embedded r2000 | Time to revision 136 days |
| 2025-06-27 | same kind of change as the line above | CVE-2024-21925 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded r1000 | Time to revision 136 days |
| 2025-06-27 | same kind of change as the line above | CVE-2024-21925 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded r2000 | Time to revision 136 days |
| 2025-06-27 | same kind of change as the line above | CVE-2024-21925 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded v1000 | Time to revision 136 days |
| 6 more rows in this change are not listed here. Open all 14 rows → | |||||
| Tue 11 Feb 2025· 2 changes | |||||
| 2025-02-11 | Product added | CVE-2023-31356 | not named as affected at publication, now names amd epyc™ embedded 7003 and 1 more | Time to revision 182 days | |
| 2025-02-11 | same kind of change as the line above | CVE-2023-31356 | same vendor as the line above | not named as affected at publication, now names amd epyc™ embedded 7003 | Time to revision 182 days |
| 2025-02-11 | same kind of change as the line above | CVE-2023-31356 | same vendor as the line above | not named as affected at publication, now names amd epyc™ embedded 9004 | Time to revision 182 days |
| Tue 18 Jun 2024· 4 changes | |||||
| 2024-06-18 | Product added | CVE-2023-20533 | not named as affected at publication, now names amd epyc™ embedded 7002 | Time to revision 217 days | |
| 2024-06-18 | Product added | not named as affected at publication, now names amd epyc™ embedded 7003 | Time to revision 217 days | ||
| 2024-06-18 | same kind of change as the line above | CVE-2023-20533 | same vendor as the line above | same change as the line above | Time to revision 217 days |
| 2024-06-18 | same kind of change as the line above | CVE-2023-20566 | same vendor as the line above | same change as the line above | Time to revision 217 days |
| 2024-06-18 | Product added | CVE-2023-20566 | not named as affected at publication, now names amd epyc™ embedded 9003 | Time to revision 217 days | |
| Tue 13 Feb 2024· 17 changes | |||||
| 2024-02-13 | Product added | 17 rows, one per record and product | not named as affected at publication, now names amd epyc™ embedded 3000 and 13 more | Time to revision 91 days | |
| 2024-02-13 | same kind of change as the line above | CVE-2023-20521 | same vendor as the line above | not named as affected at publication, now names amd epyc™ embedded 3000 | Time to revision 91 days |
| 2024-02-13 | same kind of change as the line above | CVE-2023-20521 | same vendor as the line above | not named as affected at publication, now names amd epyc™ embedded 7002 | Time to revision 91 days |
| 2024-02-13 | same kind of change as the line above | CVE-2023-20521 | same vendor as the line above | not named as affected at publication, now names amd epyc™ embedded 7003 | Time to revision 91 days |
| 2024-02-13 | same kind of change as the line above | CVE-2023-20521 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded r1000 | Time to revision 91 days |
| 2024-02-13 | same kind of change as the line above | CVE-2023-20521 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded r2000 | Time to revision 91 days |
| 2024-02-13 | same kind of change as the line above | CVE-2023-20521 | same vendor as the line above | not named as affected at publication, now names amd ryzen™ embedded v1000 | Time to revision 91 days |
| 2024-02-13 | same kind of change as the line above | CVE-2023-20526 | same vendor as the line above | not named as affected at publication, now names amd epyc™ embedded 3000 | Time to revision 91 days |
| 2024-02-13 | same kind of change as the line above | CVE-2023-20526 | same vendor as the line above | not named as affected at publication, now names amd epyc™ embedded 7002 | Time to revision 91 days |
| 9 more rows in this change are not listed here. Open all 17 rows → | |||||
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 →