Skip to content

Product added

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

24 changes behind one line · newest firstCSVJSONRSS

SinceClear all

One change, in full: Product added: 6 products named as affected from microsoft. The same change in 4 CVE records, across 6 products: 24 rows in all. Drawn here as 4 lines, one per product. Back to the ledger

Counted changes of "Product added" from microsoft, 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.
2026-07-15CVE-2026-47304not named as affected at publication, now names microsoft .net framework 3.5 and 5 moreTime to revision 1 days
2026-07-15CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5Time to revision 1 days
2026-07-15CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2Time to revision 1 days
2026-07-15CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8Time to revision 1 days
2026-07-15CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1Time to revision 1 days
2026-07-15CVE-2026-47304same 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 1 days
2026-07-15CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.8Time to revision 1 days
2026-07-15CVE-2026-50525not named as affected at publication, now names microsoft .net framework 3.5 and 5 moreTime to revision 1 days
2026-07-15CVE-2026-50525same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5Time to revision 1 days
2026-07-15CVE-2026-50525same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2Time to revision 1 days
2026-07-15CVE-2026-50525same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8Time to revision 1 days
2026-07-15CVE-2026-50525same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1Time to revision 1 days
2026-07-15CVE-2026-50525same 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 1 days
2026-07-15CVE-2026-50525same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.8Time to revision 1 days
2026-07-15CVE-2026-50649not named as affected at publication, now names microsoft .net framework 3.5 and 5 moreTime to revision 1 days
2026-07-15CVE-2026-50649same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5Time to revision 1 days
2026-07-15CVE-2026-50649same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2Time to revision 1 days
2026-07-15CVE-2026-50649same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8Time to revision 1 days
2026-07-15CVE-2026-50649same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1Time to revision 1 days
2026-07-15CVE-2026-50649same 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 1 days
2026-07-15CVE-2026-50649same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.8Time to revision 1 days
2026-07-15CVE-2026-50659not named as affected at publication, now names microsoft .net framework 3.5 and 5 moreTime to revision 1 days
2026-07-15CVE-2026-50659same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5Time to revision 1 days
2026-07-15CVE-2026-50659same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2Time to revision 1 days
2026-07-15CVE-2026-50659same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8Time to revision 1 days
2026-07-15CVE-2026-50659same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1Time to revision 1 days
2026-07-15CVE-2026-50659same 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 1 days
2026-07-15CVE-2026-50659same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.8Time to revision 1 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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

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 →