Skip to content

Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

12 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

Showing changes seen on 2026-06-05. Every day

Counted changes changed on 2026-06-05, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
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.KindRecord, 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 changedDays 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 record changes
2026-06-05Fix version movedCVE-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.Days to revision 24
2026-06-05Affected range extendedCVE-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.Days to revision 9
2026-06-05Product addedCVE-2025-5914not named as affected at publication, now names openshift file integrity operator - fio 1Days to revision 360
2026-06-05Product addedCVE-2026-33999not named as affected at publication, now names red hat enterprise linux 6 extended lifecycle support - extensionDays to revision 42
2026-06-05Product addedCVE-2026-34000not named as affected at publication, now names red hat enterprise linux 6 extended lifecycle support - extensionDays to revision 30
2026-06-05Product addedCVE-2026-34001not named as affected at publication, now names red hat enterprise linux 6 extended lifecycle support - extensionDays to revision 42
2026-06-05Product addedCVE-2026-34002not named as affected at publication, now names red hat enterprise linux 6 extended lifecycle support - extensionDays to revision 30
2026-06-05Product addedCVE-2026-34003not named as affected at publication, now names red hat enterprise linux 6 extended lifecycle support - extensionDays to revision 42
2026-06-05CVSS base score changedCVE-2026-42250
whole record
CERT-PL
stated at publication 5.1, now states 4.8CVSS v4.0 · base scoreMediumMediumDays to revision 8
2026-06-05Record state changedCVE-2026-6207
whole record
TR-CERT
stated at publication PUBLISHED, now states REJECTEDDays to revision 0
2026-06-05Record state changedCVE-2026-6208
whole record
TR-CERT
stated at publication PUBLISHED, now states REJECTEDDays to revision 0
2026-06-05Record state changedCVE-2026-6209
whole record
TR-CERT
stated at publication PUBLISHED, now states REJECTEDDays 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.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 03:47 UTC · scroll for earlierfewermore

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 →

Check my CVEs against these changes →