Every change, newest first

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

35 changes · newest first · grouped by dayCSV JSON RSS

Counted changes published by TPLink, 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.
Thu 27 Aug 2026· 1 record change
2026-08-27	Product added	CVE-2026-15315	tp-link systems inc TPLink	not named as affected at publication, now names tapo c120 v1	Days to revision 9
Tue 25 Aug 2026· 3 record changes
2026-08-25	Product added	CVE-2026-12339	tp-link systems inc. TPLink	not named as affected at publication, now names tl-mr100 v3.20	Days to revision 15
2026-08-25	Product added	CVE-2026-12339	tp-link systems inc. TPLink	not named as affected at publication, now names tl-mr150 v3.20	Days to revision 15
2026-08-25	Product added	CVE-2026-12339	tp-link systems inc. TPLink	not named as affected at publication, now names tl-mr6400 v8.0	Days to revision 15
Wed 19 Aug 2026· 2 record changes
2026-08-19	Product added	CVE-2026-34118	tp link systems inc. TPLink	not named as affected at publication, now names tapo c100 v5	Days to revision 139
2026-08-19	Product added	CVE-2026-34118	tp link systems inc. TPLink	not named as affected at publication, now names tapo c101 v5	Days to revision 139
Fri 14 Aug 2026· 1 record change
2026-08-14	Product added	CVE-2025-14300	tp link systems inc. TPLink	not named as affected at publication, now names tapo c425 v1.2	Days to revision 238
Tue 11 Aug 2026· 1 record change
2026-08-11	Product added	CVE-2026-12001	tp link systems inc. TPLink	not named as affected at publication, now names tl-wr902ac v4	Days to revision 15
Tue 4 Aug 2026· 1 record change
2026-08-04	Product added	CVE-2026-0651	tp link systems inc. TPLink	not named as affected at publication, now names tapo c211 v2	Days to revision 175
Fri 31 Jul 2026· 1 record change
2026-07-31	Product added	CVE-2026-0631	tp-link systems inc. TPLink	not named as affected at publication, now names archer axe75 v1	Days to revision 179
Mon 13 Jul 2026· 2 record changes
2026-07-13	Product added	CVE-2025-15608	tp-link systems inc. TPLink	not named as affected at publication, now names ax55 v4	Days to revision 115
2026-07-13	Product added	CVE-2025-15608	tp-link systems inc. TPLink	not named as affected at publication, now names ax55 v4.6	Days to revision 115
Thu 4 Jun 2026· 1 record change
2026-06-04	Product added	CVE-2026-22226	tp link systems inc. TPLink	not named as affected at publication, now names archer ax73 v2	Days to revision 122
Wed 29 Apr 2026· 1 record change
2026-04-29	Product added	CVE-2026-0919	tp link systems inc. TPLink	not named as affected at publication, now names tapo c210 v3	Days to revision 92
Thu 23 Apr 2026· 1 record change
2026-04-23	Product added	CVE-2026-0834	tp link systems inc. TPLink	not named as affected at publication, now names tl-wr841n v13	Days to revision 92
Wed 22 Apr 2026· 3 record changes
2026-04-22	Product added	CVE-2025-15551	tp-link systems inc. TPLink	not named as affected at publication, now names archer c20 v5	Days to revision 76
2026-04-22	Product added	CVE-2025-6982	tp-link systems inc. TPLink	not named as affected at publication, now names archer c20 v5	Days to revision 280
2026-04-22	Product added	CVE-2026-0834	tp-link systems inc. TPLink	not named as affected at publication, now names archer c20 v5	Days to revision 91
Fri 3 Apr 2026· 1 record change
2026-04-03	Product added	CVE-2025-14300	tp link systems inc. TPLink	not named as affected at publication, now names tapo c100 v5	Days to revision 105
Thu 2 Apr 2026· 4 record changes
2026-04-02	Product added	CVE-2025-8065	tp-link systems inc. TPLink	not named as affected at publication, now names tapo c520ws v2.6	Days to revision 104
2026-04-02	Product added	CVE-2026-0651	tp link systems inc. TPLink	not named as affected at publication, now names tapo c520ws v2.6	Days to revision 51
2026-04-02	CVSS base score changed	CVE-2025-8065	whole record TPLink	stated at publication 7.1, now states 8.7CVSS v4.0 · base scoreHighHigh	Days to revision 104
2026-04-02	CVSS base score changed	CVE-2026-0651	whole record TPLink	stated at publication 5.3, now states 6.9CVSS v4.0 · base scoreMediumMedium	Days to revision 51
Thu 19 Mar 2026· 4 record changes
2026-03-19	Product added	CVE-2026-0630	tp link systems inc. TPLink	not named as affected at publication, now names axe75 v1.0	Days to revision 45
2026-03-19	Product added	CVE-2026-22225	tp link systems inc. TPLink	not named as affected at publication, now names archer ax53 v1.0	Days to revision 45
2026-03-19	Product added	CVE-2025-53711	tp link systems inc. TPLink	not named as affected at publication, now names tl-wr842nd v2	Days to revision 233
2026-03-19	Product added	CVE-2025-53711	tp link systems inc. TPLink	not named as affected at publication, now names tl-wr949n v3	Days to revision 233
Fri 13 Mar 2026· 2 record changes
2026-03-13	Product added	CVE-2026-0651	tp-link systems inc. TPLink	not named as affected at publication, now names tapo d235 v1	Days to revision 31
2026-03-13	Product added	CVE-2026-0653	tp-link systems inc. TPLink	not named as affected at publication, now names tapo d235 v1	Days to revision 31
Mon 2 Mar 2026· 1 record change
2026-03-02	Product added	CVE-2026-22229	tp-link systems inc. TPLink	not named as affected at publication, now names deco be25 v1.0	Days to revision 28
Mon 9 Feb 2026· 1 record change
2026-02-09	Product added	CVE-2026-0918	tp-link systems inc. TPLink	not named as affected at publication, now names tapo c100 v5	Days to revision 13
Tue 27 Jan 2026· 1 record change
2026-01-27	Fix version moved	CVE-2025-14756	tp-link systems inc.archer mr600 v5.0 TPLink	stated at publication 1.0.0 0.9.1 v0001.0 Build 250930 Rel.63611n, now states 1.1.0 0.9.1 v0001.0 Build 250930 Rel.63611nRelease branch starts at 0.same day	Days to revision 0
Wed 21 Jan 2026· 1 record change
2026-01-21	CVSS base score changed	CVE-2026-0834	whole record TPLink	stated at publication 5.3, now states 7.2CVSS v4.0 · base scoreMediumHigh	Days to revision 0
Fri 9 Jan 2026· 1 record change
2026-01-09	Product added	CVE-2025-14553	tp-link systems inc. TPLink	not named as affected at publication, now names tp-link tapo app	Days to revision 23
Wed 23 Jul 2025· 1 record change
2025-07-23	CVSS base score changed	CVE-2025-7724	whole record TPLink	stated at publication 9.3, now states 8.7CVSS v4.0 · base scoreCriticalHigh	Days to revision 1

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.

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 →