Every change, newest first

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

47 changes · newest first · grouped by dayCSV JSON RSS

SinceKindVendorSortClear all

PublisherPublishedChangedSourceRows

Showing changes seen on 2026-01-14. Every day

Counted changes from fortinet, published by fortinet, changed on 2026-01-14, 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 14 Jan 2026· 47 record changes
2026-01-142 commits	Affected range extended	Show all 4 CVE records in this change: Affected range extended: 4.0.5 → 4.0.6 from fortinetHide the 4 CVE records in this change: Affected range extended: 4.0.5 → 4.0.6 from fortinet	fortinetfortisandbox	stated at publication 4.0.5, now states 4.0.6Branches and original-value intervals are stated on each row.	Days to revision 491 to 645
2026-01-14	same kind of change as the line above	CVE-2023-47541	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Days to revision 645
2026-01-14	same kind of change as the line above	CVE-2024-31487	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Days to revision 645
2026-01-14	same kind of change as the line above	CVE-2023-47540	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Days to revision 645
2026-01-14	same kind of change as the line above	CVE-2024-31490	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Days to revision 491
2026-01-14	Affected range extended	CVE-2023-26210	fortinetfortiadc	stated at publication 7.0.5, now states 7.0.6Release branch starts at 7.0.0.	Days to revision 946
2026-01-142 commits	Affected range extended	Show all 3 CVE records in this change: Affected range extended: 4.0.4 → 4.0.6 from fortinetHide the 3 CVE records in this change: Affected range extended: 4.0.4 → 4.0.6 from fortinet	fortinetfortisandbox	stated at publication 4.0.4, now states 4.0.6Branches and original-value intervals are stated on each row.	Days to revision 763 to 824
2026-01-14	same kind of change as the line above	CVE-2023-41836	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Days to revision 824
2026-01-14	same kind of change as the line above	CVE-2023-45587	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Days to revision 763
2026-01-14	same kind of change as the line above	CVE-2023-41844	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Days to revision 763
2026-01-14	Affected range extended	CVE-2023-40721	fortinetfortios	stated at publication 6.2.16, now states 6.2.17Release branch starts at 6.2.0.	Days to revision 337
2026-01-14	Affected range extended	CVE-2023-40721	fortinetfortios	stated at publication 6.4.15, now states 6.4.16Release branch starts at 6.4.0.	Days to revision 337
2026-01-14	Affected range extended	CVE-2023-29175	fortinetfortios	stated at publication 6.2.15, now states 6.2.17Release branch starts at 6.2.0.	Days to revision 946
2026-01-14	Affected range extended	CVE-2023-29175	fortinetfortios	stated at publication 6.4.13, now states 6.4.16Release branch starts at 6.4.0.	Days to revision 946
2026-01-14	Affected range extended	CVE-2023-29175	fortinetfortios	stated at publication 6.0.17, now states 6.0.18Release branch starts at 6.0.0.	Days to revision 946
2026-01-14	Affected range extended	CVE-2023-29175	fortinetfortiproxy	stated at publication 2.0.12, now states 2.0.14Release branch starts at 2.0.0.	Days to revision 946
2026-01-14	Affected range extended	CVE-2023-41842Show all 2 products in this change: Affected range extended: 6.2.12 → 6.2.13 in CVE-2023-41842Hide the 2 products in this change: Affected range extended: 6.2.12 → 6.2.13 in CVE-2023-41842	fortinet2 products	stated at publication 6.2.12, now states 6.2.13Release branch starts at 6.2.0.	Days to revision 673
2026-01-14	same kind of change as the line above	CVE-2023-41842	same vendor as the line above	same change as the line aboveRelease branch starts at 6.2.0.	Days to revision 673
2026-01-14	same kind of change as the line above	CVE-2023-41842	same vendor as the line above	same change as the line aboveRelease branch starts at 6.2.0.	Days to revision 673
2026-01-14	Affected range extended	CVE-2023-41842Show all 2 products in this change: Affected range extended: 6.4.14 → 6.4.15 in CVE-2023-41842Hide the 2 products in this change: Affected range extended: 6.4.14 → 6.4.15 in CVE-2023-41842	fortinet2 products	stated at publication 6.4.14, now states 6.4.15Release branch starts at 6.4.0.	Days to revision 673
2026-01-14	same kind of change as the line above	CVE-2023-41842	same vendor as the line above	same change as the line aboveRelease branch starts at 6.4.0.	Days to revision 673
2026-01-14	same kind of change as the line above	CVE-2023-41842	same vendor as the line above	same change as the line aboveRelease branch starts at 6.4.0.	Days to revision 673
2026-01-14	Affected range extended	CVE-2024-48885	fortinetfortiweb	stated at publication 7.2.10, now states 7.2.12Release branch starts at 7.2.0.	Days to revision 363
2026-01-14	Affected range extended	CVE-2024-48885	fortinetfortiweb	stated at publication 7.0.10, now states 7.0.12Release branch starts at 7.0.0.	Days to revision 363
2026-01-142 commits	Affected range extended	Show all 6 CVE records in this change: Affected range extended: 7.0.17 → 7.0.18 from fortinetHide the 6 CVE records in this change: Affected range extended: 7.0.17 → 7.0.18 from fortinet	fortinetfortios	stated at publication 7.0.17, now states 7.0.182 release branches. Branches and original-value intervals are stated on each row.	Days to revision 92 to 104
2026-01-14	same kind of change as the line above	CVE-2025-57740	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 92
2026-01-14	same kind of change as the line above	CVE-2024-26008	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 92
2026-01-14	same kind of change as the line above	CVE-2025-22862	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.6.	Days to revision 104
2026-01-14	same kind of change as the line above	CVE-2025-58903	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 92
2026-01-14	same kind of change as the line above	CVE-2025-25253	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 92
2026-01-14	same kind of change as the line above	CVE-2023-46718	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 92
2026-01-142 commits	Affected range extended	Show all 6 CVE records in this change: Affected range extended: 7.0.21 → 7.0.22 from fortinetHide the 6 CVE records in this change: Affected range extended: 7.0.21 → 7.0.22 from fortinet	fortinetfortiproxy	stated at publication 7.0.21, now states 7.0.222 release branches. Branches and original-value intervals are stated on each row.	Days to revision 92 to 104
2026-01-14	same kind of change as the line above	CVE-2025-57740	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 92
2026-01-14	same kind of change as the line above	CVE-2024-26008	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 92
2026-01-14	same kind of change as the line above	CVE-2025-54822	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 92
2026-01-14	same kind of change as the line above	CVE-2025-22862	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.5.	Days to revision 104
2026-01-14	same kind of change as the line above	CVE-2025-25253	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 92
2026-01-14	same kind of change as the line above	CVE-2023-46718	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 92
2026-01-14	Affected range extended	CVE-2025-53845	fortinetfortianalyzer	stated at publication 7.0.14, now states 7.0.15Release branch starts at 7.0.0.	Days to revision 92
2026-01-14	Affected range extended	CVE-2024-46669	fortinetfortios	stated at publication 7.2.10, now states 7.2.11Release branch starts at 7.2.0.	Days to revision 365
2026-01-14	Affected range extended	Show all 2 CVE records in this change: Affected range extended: 7.2.8 → 7.2.9 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.2.8 → 7.2.9 from fortinet	fortinetfortimail	stated at publication 7.2.8, now states 7.2.9Release branch starts at 7.2.0.	Days to revision 57 to 155
2026-01-14	same kind of change as the line above	CVE-2024-40588	same vendor as the line above	same change as the line aboveRelease branch starts at 7.2.0.	Days to revision 155
2026-01-14	same kind of change as the line above	CVE-2025-54972	same vendor as the line above	same change as the line aboveRelease branch starts at 7.2.0.	Days to revision 57
2026-01-14	Affected range extended	Show all 2 CVE records in this change: Affected range extended: 7.0.11 → 7.0.12 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.0.11 → 7.0.12 from fortinet	fortinetfortiweb	stated at publication 7.0.11, now states 7.0.122 release branches. Branches and original-value intervals are stated on each row.	Days to revision 92 to 127
2026-01-14	same kind of change as the line above	CVE-2025-53609	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.2.	Days to revision 127
2026-01-14	same kind of change as the line above	CVE-2024-47569	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Days to revision 92
2026-01-14	Affected range extended	CVE-2025-58324	fortinetfortisiem	stated at publication 7.1.8, now states 7.1.9Release branch starts at 7.1.0.	Days to revision 92
2026-01-14	Affected range extended	CVE-2024-47569	fortinetfortiweb	stated at publication 7.2.11, now states 7.2.12Release branch starts at 7.2.0.	Days to revision 92
2026-01-14	Product added	CVE-2024-54026	fortinet	not named as affected at publication, now names fortisandbox cloud	Days to revision 309
2026-01-14	Product added	CVE-2023-41842	fortinet	not named as affected at publication, now names fortianalyzer-bigdata	Days to revision 673
2026-01-142 commits	Product added	Show all 3 CVE records in this change: Product added: fortimanager cloud named as affected from fortinetHide the 3 CVE records in this change: Product added: fortimanager cloud named as affected from fortinet	fortinet	not named as affected at publication, now names fortimanager cloudBranches and original-value intervals are stated on each row.	Days to revision 92 to 365
2026-01-14	same kind of change as the line above	CVE-2024-48884	same vendor as the line above	same change as the line above	Days to revision 365
2026-01-14	same kind of change as the line above	CVE-2024-50566	same vendor as the line above	same change as the line above	Days to revision 365
2026-01-14	same kind of change as the line above	CVE-2024-47569	same vendor as the line above	same change as the line above	Days to revision 92
2026-01-14	Product added	Show all 2 CVE records in this change: Product added: fortisase named as affected from fortinetHide the 2 CVE records in this change: Product added: fortisase named as affected from fortinet	fortinet	not named as affected at publication, now names fortisase	Days to revision 92
2026-01-14	same kind of change as the line above	CVE-2025-31366	same vendor as the line above	same change as the line above	Days to revision 92
2026-01-14	same kind of change as the line above	CVE-2025-47890	same vendor as the line above	same change as the line above	Days to revision 92

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

Every kind of change

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub advisory

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 →