Skip to content

Product added

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

8 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "Product added" published by TPLink, from the last 30 days, 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.
Thu 27 Aug 2026· 1 record change
2026-08-27CVE-2026-15315TPLinknot named as affected at publication, now names tapo c120 v1Days to revision 9
Tue 25 Aug 2026· 3 record changes
2026-08-25CVE-2026-12339TPLinknot named as affected at publication, now names tl-mr100 v3.20 and 2 moreDays to revision 15
2026-08-25CVE-2026-12339same vendor as the line abovenot named as affected at publication, now names tl-mr100 v3.20Days to revision 15
2026-08-25CVE-2026-12339same vendor as the line abovenot named as affected at publication, now names tl-mr150 v3.20Days to revision 15
2026-08-25CVE-2026-12339same vendor as the line abovenot named as affected at publication, now names tl-mr6400 v8.0Days to revision 15
Wed 19 Aug 2026· 2 record changes
2026-08-19CVE-2026-34118TPLinknot named as affected at publication, now names tapo c100 v5 and 1 moreDays to revision 139
2026-08-19CVE-2026-34118same vendor as the line abovenot named as affected at publication, now names tapo c100 v5Days to revision 139
2026-08-19CVE-2026-34118same vendor as the line abovenot named as affected at publication, now names tapo c101 v5Days to revision 139
Fri 14 Aug 2026· 1 record change
2026-08-14CVE-2025-14300TPLinknot named as affected at publication, now names tapo c425 v1.2Days to revision 238
Tue 11 Aug 2026· 1 record change
2026-08-11CVE-2026-12001TPLinknot named as affected at publication, now names tl-wr902ac v4Days to revision 15

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. 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.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
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 →