Skip to content

Affected range extended

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

45 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

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

Counted changes of "Affected range extended" 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.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 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 14 Jan 2026· 45 changes
2026-01-14CVE-2026-22194
gestsupgestsup
VulnCheck
stated at publication 3.2.56, now states 3.2.60Release branch starts at 0.Time to revision 5 days
2026-01-14CVE-2026-22195
gestsupgestsup
VulnCheck
stated at publication 3.2.56, now states 3.2.60Release branch starts at 0.Time to revision 5 days
2026-01-14CVE-2026-22197
gestsupgestsup
VulnCheck
stated at publication 3.2.56, now states 3.2.60Release branch starts at 0.Time to revision 5 days
2026-01-14CVE-2026-22198
gestsupgestsup
VulnCheck
stated at publication 3.2.56, now states 3.2.60Release branch starts at 0.Time to revision 5 days
2026-01-14CVE-2026-22196
gestsupgestsup
VulnCheck
stated at publication 3.2.56, now states 3.2.60Release branch starts at 0.Time to revision 5 days
2026-01-14CVE-2023-47541
fortinetfortisandbox
stated at publication 4.0.5, now states 4.0.6Release branch starts at 4.0.0.Time to revision 645 days
2026-01-14CVE-2023-26210
fortinetfortiadc
stated at publication 7.0.5, now states 7.0.6Release branch starts at 7.0.0.Time to revision 946 days
2026-01-14CVE-2023-41836
fortinetfortisandbox
stated at publication 4.0.4, now states 4.0.6Release branch starts at 4.0.0.Time to revision 824 days
2026-01-14CVE-2023-40721
fortinetfortios
stated at publication 6.2.16, now states 6.2.17Release branch starts at 6.2.0.Time to revision 337 days
2026-01-14CVE-2023-40721
fortinetfortios
stated at publication 6.4.15, now states 6.4.16Release branch starts at 6.4.0.Time to revision 337 days
2026-01-14CVE-2023-29175
fortinetfortios
stated at publication 6.2.15, now states 6.2.17Release branch starts at 6.2.0.Time to revision 946 days
2026-01-14CVE-2023-29175
fortinetfortios
stated at publication 6.4.13, now states 6.4.16Release branch starts at 6.4.0.Time to revision 946 days
2026-01-14CVE-2023-29175
fortinetfortios
stated at publication 6.0.17, now states 6.0.18Release branch starts at 6.0.0.Time to revision 946 days
2026-01-14CVE-2023-29175
fortinetfortiproxy
stated at publication 2.0.12, now states 2.0.14Release branch starts at 2.0.0.Time to revision 946 days
2026-01-14CVE-2023-45587
fortinetfortisandbox
stated at publication 4.0.4, now states 4.0.6Release branch starts at 4.0.0.Time to revision 763 days
2026-01-14CVE-2023-41844
fortinetfortisandbox
stated at publication 4.0.4, now states 4.0.6Release branch starts at 4.0.0.Time to revision 763 days
2026-01-14CVE-2023-41842
fortinetfortianalyzer
stated at publication 6.2.12, now states 6.2.13Release branch starts at 6.2.0.Time to revision 673 days
2026-01-14CVE-2023-41842
fortinetfortianalyzer
stated at publication 6.4.14, now states 6.4.15Release branch starts at 6.4.0.Time to revision 673 days
2026-01-14CVE-2023-41842
fortinetfortimanager
stated at publication 6.2.12, now states 6.2.13Release branch starts at 6.2.0.Time to revision 673 days
2026-01-14CVE-2023-41842
fortinetfortimanager
stated at publication 6.4.14, now states 6.4.15Release branch starts at 6.4.0.Time to revision 673 days
2026-01-14CVE-2024-31487
fortinetfortisandbox
stated at publication 4.0.5, now states 4.0.6Release branch starts at 4.0.0.Time to revision 645 days
2026-01-14CVE-2023-47540
fortinetfortisandbox
stated at publication 4.0.5, now states 4.0.6Release branch starts at 4.0.0.Time to revision 645 days
2026-01-14CVE-2024-31490
fortinetfortisandbox
stated at publication 4.0.5, now states 4.0.6Release branch starts at 4.0.0.Time to revision 491 days
2026-01-14CVE-2024-48885
fortinetfortiweb
stated at publication 7.2.10, now states 7.2.12Release branch starts at 7.2.0.Time to revision 363 days
2026-01-14CVE-2024-48885
fortinetfortiweb
stated at publication 7.0.10, now states 7.0.12Release branch starts at 7.0.0.Time to revision 363 days
2026-01-14CVE-2025-57740
fortinetfortios
stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0.Time to revision 92 days
2026-01-14CVE-2025-57740
fortinetfortiproxy
stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.0.Time to revision 92 days
2026-01-14CVE-2024-26008
fortinetfortios
stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0.Time to revision 92 days
2026-01-14CVE-2024-26008
fortinetfortiproxy
stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.0.Time to revision 92 days
2026-01-14CVE-2025-53845
fortinetfortianalyzer
stated at publication 7.0.14, now states 7.0.15Release branch starts at 7.0.0.Time to revision 92 days
2026-01-14CVE-2025-54822
fortinetfortiproxy
stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.0.Time to revision 92 days
2026-01-14CVE-2024-46669
fortinetfortios
stated at publication 7.2.10, now states 7.2.11Release branch starts at 7.2.0.Time to revision 365 days
2026-01-14CVE-2024-40588
fortinetfortimail
stated at publication 7.2.8, now states 7.2.9Release branch starts at 7.2.0.Time to revision 155 days
2026-01-14CVE-2025-53609
fortinetfortiweb
stated at publication 7.0.11, now states 7.0.12Release branch starts at 7.0.2.Time to revision 127 days
2026-01-14CVE-2025-22862
fortinetfortios
stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.6.Time to revision 104 days
2026-01-14CVE-2025-22862
fortinetfortiproxy
stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.5.Time to revision 104 days
2026-01-14CVE-2025-58903
fortinetfortios
stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0.Time to revision 92 days
2026-01-14CVE-2025-58324
fortinetfortisiem
stated at publication 7.1.8, now states 7.1.9Release branch starts at 7.1.0.Time to revision 92 days
2026-01-14CVE-2025-25253
fortinetfortios
stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0.Time to revision 92 days
2026-01-14CVE-2025-25253
fortinetfortiproxy
stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.0.Time to revision 92 days
2026-01-14CVE-2023-46718
fortinetfortios
stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0.Time to revision 92 days
2026-01-14CVE-2023-46718
fortinetfortiproxy
stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.0.Time to revision 92 days
2026-01-14CVE-2024-47569
fortinetfortiweb
stated at publication 7.2.11, now states 7.2.12Release branch starts at 7.2.0.Time to revision 92 days
2026-01-14CVE-2024-47569
fortinetfortiweb
stated at publication 7.0.11, now states 7.0.12Release branch starts at 7.0.0.Time to revision 92 days
2026-01-14CVE-2025-54972
fortinetfortimail
stated at publication 7.2.8, now states 7.2.9Release branch starts at 7.2.0.Time to revision 57 days

This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller.

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 →