Every change, newest first
Showing changes seen on 2026-06-05. 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 5 Jun 2026· 12 changes | |||||
| 2026-06-05 | Fix version moved | CVE-2026-32177 | microsoftmicrosoft visual studio 2022 version 17.14 | stated at publication 17.14.31, now states 17.14.32Release branch starts at 17.14.0. | Time to revision 24 days |
| 2026-06-05 | Affected range extended | CVE-2024-58135 | srimojolicious CPANSec | stated at publication 9.39, now states 9.45Release branch starts at 7.28.Original value first replaced 2025-05-12; this value first seen 2026-06-05. | Time to revision 9 days |
| 2026-06-05 | Product added | CVE-2025-5914 | not named as affected at publication, now names openshift file integrity operator - fio 1 | Time to revision 360 days | |
| 2026-06-05 | Product added | not named as affected at publication, now names red hat enterprise linux 6 extended lifecycle support - extension | Time to revision 30 to 42 days | ||
| 2026-06-05 | same kind of change as the line above | CVE-2026-33999 | same vendor as the line above | same change as the line above | Time to revision 42 days |
| 2026-06-05 | same kind of change as the line above | CVE-2026-34000 | same vendor as the line above | same change as the line above | Time to revision 30 days |
| 2026-06-05 | same kind of change as the line above | CVE-2026-34001 | same vendor as the line above | same change as the line above | Time to revision 42 days |
| 2026-06-05 | same kind of change as the line above | CVE-2026-34002 | same vendor as the line above | same change as the line above | Time to revision 30 days |
| 2026-06-05 | same kind of change as the line above | CVE-2026-34003 | same vendor as the line above | same change as the line above | Time to revision 42 days |
| 2026-06-05 | CVSS base score changed | CVE-2026-42250 | whole record CERT-PL | stated at publication 5.1, now states 4.8CVSS v4.0 · base scoreMediumMedium | Time to revision 8 days |
| 2026-06-05 | Record state changed | whole record TR-CERT | stated at publication PUBLISHED, now states REJECTED | Time to revision 0 days | |
| 2026-06-05 | same kind of change as the line above | CVE-2026-6207 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-06-05 | same kind of change as the line above | CVE-2026-6208 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-06-05 | same kind of change as the line above | CVE-2026-6209 | same vendor as the line above | same change as the line above | Time to revision 0 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 →