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. |
|---|---|---|---|---|---|
| Mon 30 Mar 2026· 1 record change | |||||
| 2026-03-30 | Affected range extended | CVE-2026-23813 | hpe | stated at publication 10.13.1101, now states 10.13.1160Release branch starts at 10.13.0000. | Days to revision 20 |
| Tue 24 Jun 2025· 18 record changes | |||||
| 2025-06-247 commits | Product added | hpe | not named as affected at publication, now names aos-8 instant and aos-10 apBranches and original-value intervals are stated on each row. | Days to revision 406 | |
| 2025-06-24 | same kind of change as the line above | CVE-2024-31480 | same vendor as the line above | same change as the line above | Days to revision 406 |
| 2025-06-24 | same kind of change as the line above | CVE-2024-31481 | same vendor as the line above | same change as the line above | Days to revision 406 |
| 2025-06-24 | same kind of change as the line above | CVE-2024-31482 | same vendor as the line above | same change as the line above | Days to revision 406 |
| 2025-06-24 | same kind of change as the line above | CVE-2024-31483 | same vendor as the line above | same change as the line above | Days to revision 406 |
| 2025-06-24 | same kind of change as the line above | CVE-2024-31473 | same vendor as the line above | same change as the line above | Days to revision 406 |
| 2025-06-24 | same kind of change as the line above | CVE-2024-31474 | same vendor as the line above | same change as the line above | Days to revision 406 |
| 2025-06-24 | same kind of change as the line above | CVE-2024-31475 | same vendor as the line above | same change as the line above | Days to revision 406 |
| 2025-06-24 | same kind of change as the line above | CVE-2024-31476 | same vendor as the line above | same change as the line above | Days to revision 406 |
| 10 more rows in this change are not listed here. Open all 18 rows → | |||||
| Thu 13 Jun 2024· 1 record change | |||||
| 2024-06-13 | Affected range extended | CVE-2024-22441 | hewlett packard enterprise (hpe)cray system management software - pals hpe | stated at publication 1.2.13, now states 1.3.2Release branch starts at 1.0.0.same day | 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 →