Skip to content

Every change, newest first

Compare earlier and later source statements, with the dates and evidence behind each measured change.

43 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all

Showing changes seen on 2026-07-08. Every day

Counted changes changed on 2026-07-08, 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.
Wed 8 Jul 2026· 43 changes
2026-07-08Affected range extended
fortinetfortimanager
stated at publication 7.0.13, now states 7.0.16Release branch starts at 7.0.0.Time to revision 538 to 540 days
2026-07-08same kind of change as the line aboveCVE-2024-33503same vendor as the line abovesame change as the line aboveRelease branch starts at 7.0.0.Time to revision 540 days
2026-07-08same kind of change as the line aboveCVE-2024-45331same vendor as the line abovesame change as the line aboveRelease branch starts at 7.0.0.Time to revision 538 days
2026-07-08Affected range extendedCVE-2024-45331
fortinetfortianalyzer
stated at publication 7.0.13, now states 7.0.16Release branch starts at 7.0.0.Time to revision 538 days
2026-07-08Affected range extended
fortinetfortios
stated at publication 7.2.12, now states 7.2.13Release branch starts at 7.2.0.Time to revision 267 days
2026-07-08same kind of change as the line aboveCVE-2025-47890same vendor as the line abovesame change as the line aboveRelease branch starts at 7.2.0.Time to revision 267 days
2026-07-08same kind of change as the line aboveCVE-2025-31366same vendor as the line abovesame change as the line aboveRelease branch starts at 7.2.0.Time to revision 267 days
2026-07-08Affected range extended
fortinetfortiproxy
stated at publication 7.2.15, now states 7.2.16Release branch starts at 7.2.0.Time to revision 267 days
2026-07-08same kind of change as the line aboveCVE-2025-47890same vendor as the line abovesame change as the line aboveRelease branch starts at 7.2.0.Time to revision 267 days
2026-07-08same kind of change as the line aboveCVE-2025-31366same vendor as the line abovesame change as the line aboveRelease branch starts at 7.2.0.Time to revision 267 days
2026-07-08Affected range extended
fortinetfortios
stated at publication 7.0.17, now states 7.0.19Release branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.Time to revision 92 days
2026-07-08same kind of change as the line aboveCVE-2025-47890same vendor as the line abovesame change as the line aboveRelease branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.Time to revision 92 days
2026-07-08same kind of change as the line aboveCVE-2025-31366same vendor as the line abovesame change as the line aboveRelease branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.Time to revision 92 days
2026-07-08Affected range extendedCVE-2025-47890
fortinetfortiproxy
stated at publication 7.4.11, now states 7.4.14Release branch starts at 7.4.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.Time to revision 92 days
2026-07-08Affected range extended
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-07-08.Time to revision 92 days
2026-07-08same kind of change as the line aboveCVE-2025-47890same vendor as the line abovesame change as the line aboveRelease branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.Time to revision 92 days
2026-07-08same kind of change as the line aboveCVE-2025-31366same vendor as the line abovesame change as the line aboveRelease branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.Time to revision 92 days
2026-07-085 commitsProduct added23 rows, one per record and productnot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support and 4 moreBranches and original-value intervals are stated on each row.Time to revision 1 to 33 days
2026-07-08same kind of change as the line aboveCVE-2026-50256same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportTime to revision 33 days
2026-07-08same kind of change as the line aboveCVE-2026-50257same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportTime to revision 33 days
2026-07-08same kind of change as the line aboveCVE-2026-50258same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportTime to revision 33 days
2026-07-08same kind of change as the line aboveCVE-2026-50259same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportTime to revision 33 days
2026-07-08same kind of change as the line aboveCVE-2026-50260same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportTime to revision 33 days
2026-07-08same kind of change as the line aboveCVE-2026-50261same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportTime to revision 33 days
2026-07-08same kind of change as the line aboveCVE-2026-50262same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportTime to revision 33 days
2026-07-08same kind of change as the line aboveCVE-2026-50263same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportTime to revision 33 days
15 more rows in this change are not listed here. Open all 23 rows
2026-07-08Product addednot named as affected at publication, now names fortimanager cloudTime to revision 540 days
2026-07-08same kind of change as the line aboveCVE-2024-33503same vendor as the line abovesame change as the line aboveTime to revision 540 days
2026-07-08same kind of change as the line aboveCVE-2024-35276same vendor as the line abovesame change as the line aboveTime to revision 540 days
2026-07-08Product addednot named as affected at publication, now names fortianalyzer cloudTime to revision 538 to 540 days
2026-07-08same kind of change as the line aboveCVE-2024-35276same vendor as the line abovesame change as the line aboveTime to revision 540 days
2026-07-08same kind of change as the line aboveCVE-2024-45331same vendor as the line abovesame change as the line aboveTime to revision 538 days
2026-07-08Product addedCVE-2026-11610redhatnot named as affected at publication, now names 389-ds-baseTime to revision 1 days
2026-07-08Product addedCVE-2023-42789not named as affected at publication, now names fortisaseTime to revision 848 days
2026-07-08CVSS base score changedCVE-2026-60104
whole record
VulnCheck
stated at publication 8.5, now states 9.3CVSS v4.0 · base scoreHighCriticalTime to revision 0 days
2026-07-08CVSS base score changedCVE-2026-9182
whole record
Esri
stated at publication 5.3, now states 9.8CVSS v3.1 · base scoreMediumCriticalTime to revision 2 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.

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 →