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. |
|---|---|---|---|---|---|
| Tue 9 Jan 2024· 67 record changes | |||||
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 350 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 500 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 505 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 700 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e100 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e220 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e300 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e320 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e350 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e400 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e450 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e500 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e550 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names trio 8300 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names trio 8500 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 101 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 150 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 201 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 250 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 300 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 301 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 310 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 311 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 350 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 400 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 401 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 410 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 411 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 450 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 500 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 501 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 600 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 601 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 350 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 500 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 505 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 700 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e100 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e220 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e300 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e320 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e350 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e400 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e450 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e500 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e550 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names trio 8300 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names trio 8500 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 101 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 150 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 201 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 250 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 300 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 301 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 310 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 311 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 350 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 400 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 401 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 410 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 411 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 450 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 500 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 501 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 600 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 601 | Days to revision 11 |
| 2024-01-09 | Product added | CVE-2023-4468 | VulDB | not named as affected at publication, now names trio 8500 | Days to revision 11 |
| Wed 22 Nov 2023· 2 record changes | |||||
| 2023-11-22 | CVSS base score changed | CVE-2023-1009 | whole record VulDB | stated at publication 3.5, now states 6.5CVSS v3.1 · base scoreLowMedium | Days to revision 271 |
| 2023-11-22 | CVSS base score changed | CVE-2023-1163 | whole record VulDB | stated at publication 4.3, now states 6.5CVSS v3.1 · base scoreMediumMedium | Days to revision 265 |
| Tue 24 Oct 2023· 1 record change | |||||
| 2023-10-24 | Product added | CVE-2023-5152 | VulDB | not named as affected at publication, now names dar-7000 | Days to revision 30 |
| Sun 22 Oct 2023· 1 record change | |||||
| 2023-10-22 | CVSS base score changed | CVE-2023-2091 | whole record VulDB | stated at publication 5.3, now states 7.8CVSS v3.1 · base scoreMediumHigh | Days to revision 190 |
| Mon 9 Oct 2023· 2 record changes | |||||
| 2023-10-09 | Record state changed | CVE-2023-1632 | whole record VulDB | stated at publication PUBLISHED, now states REJECTED | Days to revision 198 |
| 2023-10-09 | Record state changed | CVE-2023-4413 | whole record VulDB | stated at publication PUBLISHED, now states REJECTED | Days to revision 52 |
| Sat 7 Oct 2023· 1 record change | |||||
| 2023-10-07 | Record state changed | CVE-2023-5312 | whole record VulDB | stated at publication PUBLISHED, now states REJECTED | Days to revision 2 |
| Tue 19 Sep 2023· 1 record change | |||||
| 2023-09-19 | Product added | CVE-2023-0125 | VulDB | not named as affected at publication, now names gerencia web | Days to revision 252 |
| Thu 6 Jul 2023· 1 record change | |||||
| 2023-07-06 | CVSS base score changed | CVE-2023-3529 | whole record VulDB | stated at publication 4.3, now states 5.3CVSS v3.1 · base scoreMediumMedium | Days to revision 0 |
| Mon 19 Jun 2023· 1 record change | |||||
| 2023-06-19 | Product added | CVE-2023-3311 | VulDB | not named as affected at publication, now names online-shopping-system-advanced | Days to revision 1 |
| Tue 18 Apr 2023· 1 record change | |||||
| 2023-04-18 | Product added | CVE-2023-2043 | VulDB | not named as affected at publication, now names rhid | Days to revision 4 |
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 →