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.

10 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

Showing changes seen on 2025-11-18. Every day

Counted changes changed on 2025-11-18, 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 18 Nov 2025· 10 changes
2025-11-18Affected range extendedCVE-2024-32122
fortinetfortios
stated at publication 7.2.11, now states 7.2.12Release branch starts at 7.2.0.Time to revision 224 days
2025-11-18Affected range extendedCVE-2024-32122
fortinetfortios
stated at publication 7.4.7, now states 7.4.8Release branch starts at 7.4.0.Time to revision 224 days
2025-11-18Affected range extendedCVE-2024-32122
fortinetfortios
stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0.Time to revision 224 days
2025-11-18Product addedCVE-2024-7881not named as affected at publication, now names c1-premiumTime to revision 294 days
2025-11-18Product addedCVE-2024-7881not named as affected at publication, now names c1-proTime to revision 294 days
2025-11-18Product addedCVE-2024-7881not named as affected at publication, now names c1-ultraTime to revision 294 days
2025-11-18Product addedCVE-2025-4945not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update supportTime to revision 183 days
2025-11-18Product addedCVE-2025-11021not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update supportTime to revision 53 days
2025-11-18Product addedCVE-2025-7623Supermicronot named as affected at publication, now names mbd-x13sedw-fTime to revision 0 days
2025-11-18CVSS base score changedCVE-2025-64446
whole record
fortinet
stated at publication 9.1, now states 9.4CVSS v3.1 · base scoreCriticalCriticalTime to revision 4 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

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 →