Every change, newest first

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

43 changes · newest first · grouped by dayCSV JSON RSS

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.	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.
Wed 8 Jul 2026· 43 record changes
2026-07-08	Affected range extended	Show all 2 CVE records in this change: Affected range extended: 7.0.13 → 7.0.16 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.0.13 → 7.0.16 from fortinet	fortinetfortimanager	stated at publication 7.0.13, now states 7.0.16Release branch starts at 7.0.0.	Days to revision 538 to 540
2026-07-08	same kind of change as the line above	CVE-2024-33503	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 540
2026-07-08	same kind of change as the line above	CVE-2024-45331	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 538
2026-07-08	Affected range extended	CVE-2024-45331	fortinetfortianalyzer	stated at publication 7.0.13, now states 7.0.16Release branch starts at 7.0.0.	Days to revision 538
2026-07-08	Affected range extended	Show all 2 CVE records in this change: Affected range extended: 7.2.12 → 7.2.13 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.2.12 → 7.2.13 from fortinet	fortinetfortios	stated at publication 7.2.12, now states 7.2.13Release branch starts at 7.2.0.	Days to revision 267
2026-07-08	same kind of change as the line above	CVE-2025-47890	same vendor as the line above	same change as the line aboveRelease branch starts at 7.2.0.	Days to revision 267
2026-07-08	same kind of change as the line above	CVE-2025-31366	same vendor as the line above	same change as the line aboveRelease branch starts at 7.2.0.	Days to revision 267
2026-07-08	Affected range extended	Show all 2 CVE records in this change: Affected range extended: 7.2.15 → 7.2.16 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.2.15 → 7.2.16 from fortinet	fortinetfortiproxy	stated at publication 7.2.15, now states 7.2.16Release branch starts at 7.2.0.	Days to revision 267
2026-07-08	same kind of change as the line above	CVE-2025-47890	same vendor as the line above	same change as the line aboveRelease branch starts at 7.2.0.	Days to revision 267
2026-07-08	same kind of change as the line above	CVE-2025-31366	same vendor as the line above	same change as the line aboveRelease branch starts at 7.2.0.	Days to revision 267
2026-07-08	Affected range extended	Show all 2 CVE records in this change: Affected range extended: 7.0.17 → 7.0.19 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.0.17 → 7.0.19 from fortinet	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.	Days to revision 92
2026-07-08	same kind of change as the line above	CVE-2025-47890	same vendor as the line above	same 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.	Days to revision 92
2026-07-08	same kind of change as the line above	CVE-2025-31366	same vendor as the line above	same 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.	Days to revision 92
2026-07-08	Affected range extended	CVE-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.	Days to revision 92
2026-07-08	Affected range extended	Show all 2 CVE records in this change: Affected range extended: 7.0.21 → 7.0.23 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.0.21 → 7.0.23 from fortinet	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.	Days to revision 92
2026-07-08	same kind of change as the line above	CVE-2025-47890	same vendor as the line above	same 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.	Days to revision 92
2026-07-08	same kind of change as the line above	CVE-2025-31366	same vendor as the line above	same 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.	Days to revision 92
2026-07-085 commits	Product added	Show all 12 CVE records in this change: Product added: 5 products named as affected from red hatHide the 12 CVE records in this change: Product added: 5 products named as affected from red hat23 rows, one per record and product	red hat	not 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.	Days to revision 1 to 33
2026-07-08	same kind of change as the line above	CVE-2026-50256	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Days to revision 33
2026-07-08	same kind of change as the line above	CVE-2026-50257	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Days to revision 33
2026-07-08	same kind of change as the line above	CVE-2026-50258	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Days to revision 33
2026-07-08	same kind of change as the line above	CVE-2026-50259	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Days to revision 33
2026-07-08	same kind of change as the line above	CVE-2026-50260	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Days to revision 33
2026-07-08	same kind of change as the line above	CVE-2026-50261	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Days to revision 33
2026-07-08	same kind of change as the line above	CVE-2026-50262	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Days to revision 33
2026-07-08	same kind of change as the line above	CVE-2026-50263	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Days to revision 33
15 more rows in this change are not listed here. Open all 23 rows →
2026-07-08	Product added	Show all 2 CVE records in this change: Product added: fortimanager cloud named as affected from fortinetHide the 2 CVE records in this change: Product added: fortimanager cloud named as affected from fortinet	fortinet	not named as affected at publication, now names fortimanager cloud	Days to revision 540
2026-07-08	same kind of change as the line above	CVE-2024-33503	same vendor as the line above	same change as the line above	Days to revision 540
2026-07-08	same kind of change as the line above	CVE-2024-35276	same vendor as the line above	same change as the line above	Days to revision 540
2026-07-08	Product added	Show all 2 CVE records in this change: Product added: fortianalyzer cloud named as affected from fortinetHide the 2 CVE records in this change: Product added: fortianalyzer cloud named as affected from fortinet	fortinet	not named as affected at publication, now names fortianalyzer cloud	Days to revision 538 to 540
2026-07-08	same kind of change as the line above	CVE-2024-35276	same vendor as the line above	same change as the line above	Days to revision 540
2026-07-08	same kind of change as the line above	CVE-2024-45331	same vendor as the line above	same change as the line above	Days to revision 538
2026-07-08	Product added	CVE-2026-11610	389ds redhat	not named as affected at publication, now names 389-ds-base	Days to revision 1
2026-07-08	Product added	CVE-2023-42789	fortinet	not named as affected at publication, now names fortisase	Days to revision 848
2026-07-08	CVSS base score changed	CVE-2026-60104	whole record VulnCheck	stated at publication 8.5, now states 9.3CVSS v4.0 · base scoreHighCritical	Days to revision 0
2026-07-08	CVSS base score changed	CVE-2026-9182	whole record Esri	stated at publication 5.3, now states 9.8CVSS v3.1 · base scoreMediumCritical	Days to revision 2

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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

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 →