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· 100 changes | |||||
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names ccx 350 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names ccx 500 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names ccx 505 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names ccx 700 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e100 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e220 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e300 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e320 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e350 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e400 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e450 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e500 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names edge e550 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names trio 8300 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names trio 8500 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 101 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 150 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 201 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 250 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 300 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 301 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 310 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 311 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 350 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 400 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 401 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 410 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 411 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 450 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 500 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 501 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 600 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4462 | VulDB | not named as affected at publication, now names vvx 601 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 350 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 500 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 505 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 700 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e100 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e220 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e300 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e320 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e350 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e400 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e450 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e500 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names edge e550 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names trio 8300 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names trio 8500 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 101 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 150 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 201 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 250 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 300 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 301 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 310 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 311 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 350 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 400 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 401 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 410 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 411 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 450 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 500 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 501 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 600 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4464 | VulDB | not named as affected at publication, now names vvx 601 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 350 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 500 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 505 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 700 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e100 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e220 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e300 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e320 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e350 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e400 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e450 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e500 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names edge e550 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names trio 8300 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names trio 8500 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 101 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 150 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 201 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 250 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 300 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 301 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 310 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 311 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 350 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 400 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 401 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 410 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 411 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 450 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 500 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 501 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 600 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4465 | VulDB | not named as affected at publication, now names vvx 601 | Time to revision 11 days |
| 2024-01-09 | Product added | CVE-2023-4468 | VulDB | not named as affected at publication, now names trio 8500 | Time to revision 11 days |
Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.
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 →