Skip to content

Every change, newest first

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

68 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

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

Counted changes changed on 2026-07-16, 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.
Thu 16 Jul 2026· 68 changes
2026-07-16Affected range extendedCVE-2026-59840
fortinetfortios
stated at publication 7.6.2, now states 7.6.3Release branch starts at 7.6.0.Time to revision 2 days
2026-07-16Product added42 rows, one per record and productnot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 and 5 moreTime to revision 2 days
2026-07-16same kind of change as the line aboveCVE-2026-50304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2Time to revision 2 days
2026-07-16same kind of change as the line aboveCVE-2026-50304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8Time to revision 2 days
2026-07-16same kind of change as the line aboveCVE-2026-50304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1Time to revision 2 days
2026-07-16same kind of change as the line aboveCVE-2026-50304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2Time to revision 2 days
2026-07-16same kind of change as the line aboveCVE-2026-50304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.8Time to revision 2 days
2026-07-16same kind of change as the line aboveCVE-2026-50324same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2Time to revision 2 days
2026-07-16same kind of change as the line aboveCVE-2026-50324same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8Time to revision 2 days
2026-07-16same kind of change as the line aboveCVE-2026-50324same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1Time to revision 2 days
34 more rows in this change are not listed here. Open all 42 rows
2026-07-16Product addedCVE-2026-4601
vendor not named
snyk
not named as affected at publication, now names org.webjars.npm:jsrsasignTime to revision 116 days
2026-07-16Product addedCVE-2026-10840not named as affected at publication, now names red hat openshift builds 1.8.1Time to revision 42 days
2026-07-16Product addedCVE-2024-8751SICK AGnot named as affected at publication, now names flps and 15 moreTime to revision 672 days
2026-07-16same kind of change as the line aboveCVE-2024-8751same vendor as the line abovenot named as affected at publication, now names flpsTime to revision 672 days
2026-07-16same kind of change as the line aboveCVE-2024-8751same vendor as the line abovenot named as affected at publication, now names gm32Time to revision 672 days
2026-07-16same kind of change as the line aboveCVE-2024-8751same vendor as the line abovenot named as affected at publication, now names gms800Time to revision 672 days
2026-07-16same kind of change as the line aboveCVE-2024-8751same vendor as the line abovenot named as affected at publication, now names gms800 fidorTime to revision 672 days
2026-07-16same kind of change as the line aboveCVE-2024-8751same vendor as the line abovenot named as affected at publication, now names marsic200Time to revision 672 days
2026-07-16same kind of change as the line aboveCVE-2024-8751same vendor as the line abovenot named as affected at publication, now names marsic280Time to revision 672 days
2026-07-16same kind of change as the line aboveCVE-2024-8751same vendor as the line abovenot named as affected at publication, now names marsic300Time to revision 672 days
2026-07-16same kind of change as the line aboveCVE-2024-8751same vendor as the line abovenot named as affected at publication, now names mcs100ftTime to revision 672 days
8 more rows in this change are not listed here. Open all 16 rows
2026-07-16Record state changedCVE-2026-6685
whole record
runZero
stated at publication PUBLISHED, now states REJECTEDTime to revision 15 days
2026-07-16Record state changed
whole record
@huntr_ai
stated at publication PUBLISHED, now states REJECTEDTime to revision 483 to 645 days
2026-07-16same kind of change as the line aboveCVE-2024-7033same vendor as the line abovesame change as the line aboveTime to revision 483 days
2026-07-16same kind of change as the line aboveCVE-2024-7034same vendor as the line abovesame change as the line aboveTime to revision 483 days
2026-07-16same kind of change as the line aboveCVE-2024-7038same vendor as the line abovesame change as the line aboveTime to revision 645 days
2026-07-16same kind of change as the line aboveCVE-2024-7039same vendor as the line abovesame change as the line aboveTime to revision 483 days
2026-07-16same kind of change as the line aboveCVE-2024-7040same vendor as the line abovesame change as the line aboveTime to revision 483 days
2026-07-16same kind of change as the line aboveCVE-2024-7959same vendor as the line abovesame change as the line aboveTime to revision 483 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 →