Every change, newest first
Showing changes seen on 2026-04-10. Every day
| 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. |
|---|---|---|---|---|---|
| Fri 10 Apr 2026· 23 changes | |||||
| 2026-04-10 | Fix version moved | CVE-2026-21518 | microsoftvisual studio code | stated at publication 1.109.2, now states 1.110.1Release branch starts at 1.0.0. | Time to revision 59 days |
| 2026-04-102 commits | Product added | CVE-2026-5483 | not named as affected at publication, now names red hat openshift ai 2.25 and 2 moreBranches and original-value intervals are stated on each row. | Time to revision 0 days | |
| 2026-04-10 | same kind of change as the line above | CVE-2026-5483 | same vendor as the line above | not named as affected at publication, now names red hat openshift ai 2.25 | Time to revision 0 days |
| 2026-04-10 | same kind of change as the line above | CVE-2026-5483 | same vendor as the line above | not named as affected at publication, now names red hat openshift ai 3.2 | Time to revision 0 days |
| 2026-04-10 | same kind of change as the line above | CVE-2026-5483 | same vendor as the line above | not named as affected at publication, now names red hat openshift ai 3.3 | Time to revision 0 days |
| 2026-04-10 | Product added | not named as affected at publication, now names acronis true image oem | Time to revision 192 to 953 days | ||
| 2026-04-10 | same kind of change as the line above | CVE-2023-41743 | same vendor as the line above | same change as the line above | Time to revision 953 days |
| 2026-04-10 | same kind of change as the line above | CVE-2023-44208 | same vendor as the line above | same change as the line above | Time to revision 919 days |
| 2026-04-10 | same kind of change as the line above | CVE-2023-48677 | same vendor as the line above | same change as the line above | Time to revision 850 days |
| 2026-04-10 | same kind of change as the line above | CVE-2023-5042 | same vendor as the line above | same change as the line above | Time to revision 933 days |
| 2026-04-10 | same kind of change as the line above | CVE-2024-34010 | same vendor as the line above | same change as the line above | Time to revision 711 days |
| 2026-04-10 | same kind of change as the line above | CVE-2024-34013 | same vendor as the line above | same change as the line above | Time to revision 631 days |
| 2026-04-10 | same kind of change as the line above | CVE-2024-49385 | same vendor as the line above | same change as the line above | Time to revision 463 days |
| 2026-04-10 | same kind of change as the line above | CVE-2024-55538 | same vendor as the line above | same change as the line above | Time to revision 463 days |
| 2 more rows in this change are not listed here. Open all 10 rows → | |||||
| 2026-04-10 | Product added | CVE-2026-4309 | NEC | not named as affected at publication, now names aterm gb1200pe and 3 more | Time to revision 14 days |
| 2026-04-10 | same kind of change as the line above | CVE-2026-4309 | same vendor as the line above | not named as affected at publication, now names aterm gb1200pe | Time to revision 14 days |
| 2026-04-10 | same kind of change as the line above | CVE-2026-4309 | same vendor as the line above | not named as affected at publication, now names aterm gx1200hp | Time to revision 14 days |
| 2026-04-10 | same kind of change as the line above | CVE-2026-4309 | same vendor as the line above | not named as affected at publication, now names aterm gx1200hs4 | Time to revision 14 days |
| 2026-04-10 | same kind of change as the line above | CVE-2026-4309 | same vendor as the line above | not named as affected at publication, now names aterm wg1200dm4 | Time to revision 14 days |
| 2026-04-10 | Product added | CVE-2026-4621 | NEC | not named as affected at publication, now names aterm gb1200pe and 3 more | Time to revision 14 days |
| 2026-04-10 | same kind of change as the line above | CVE-2026-4621 | same vendor as the line above | not named as affected at publication, now names aterm gb1200pe | Time to revision 14 days |
| 2026-04-10 | same kind of change as the line above | CVE-2026-4621 | same vendor as the line above | not named as affected at publication, now names aterm gx1200hp | Time to revision 14 days |
| 2026-04-10 | same kind of change as the line above | CVE-2026-4621 | same vendor as the line above | not named as affected at publication, now names aterm gx1200hs4 | Time to revision 14 days |
| 2026-04-10 | same kind of change as the line above | CVE-2026-4621 | same vendor as the line above | not named as affected at publication, now names aterm wg1200dm4 | Time to revision 14 days |
| 2026-04-10 | Product added | CVE-2026-4622 | NEC | not named as affected at publication, now names aterm gb1200pe | Time to revision 14 days |
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 →