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-02-10. Every day

Counted changes changed on 2026-02-10, 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.
Tue 10 Feb 2026· 12 record changes
2026-02-10Affected range extendedCVE-2024-47569
fortinetfortiproxy
stated at publication 7.0.21, now states 7.0.23Release branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-02-10.Days to revision 92
2026-02-10Affected range extendedCVE-2025-62631
fortinetfortios
stated at publication 7.0.18, now states 7.0.19Release branch starts at 7.0.0.Days to revision 63
2026-02-10Product addedCVE-2025-13601not named as affected at publication, now names red hat insights proxy 1.5Days to revision 76
2026-02-10Product addedCVE-2025-14104not named as affected at publication, now names red hat insights proxy 1.5Days to revision 67
2026-02-10Product addedCVE-2023-52356not named as affected at publication, now names red hat enterprise linux 10Days to revision 747
2026-02-10Product addedCVE-2026-0719not named as affected at publication, now names red hat enterprise linux 8.2 advanced update supportDays to revision 33
2026-02-10Product addedCVE-2026-0719not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportDays to revision 33
2026-02-10Product addedCVE-2026-1761not named as affected at publication, now names red hat enterprise linux 8.2 advanced update supportDays to revision 8
2026-02-10Product addedCVE-2026-1761not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportDays to revision 8
2026-02-10Product addedCVE-2025-40936not named as affected at publication, now names solid edgeDays to revision 85
2026-02-10CVSS base score changedCVE-2025-15284
whole record
harborist
stated at publication 8.7, now states 6.3CVSS v4.0 · base scoreHighMediumDays to revision 43
2026-02-10Record state changedCVE-2025-68789
whole record
Linux
stated at publication PUBLISHED, now states REJECTEDDays to revision 28

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 →