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

PublisherPublishedChangedSourceRows

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 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	Time to revision 9 days
Tue 25 Aug 2026· 3 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	Time to revision 15 days
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	Time to revision 15 days
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	Time to revision 15 days
Wed 19 Aug 2026· 2 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	Time to revision 139 days
2026-08-19	Product added	CVE-2026-34118	tp link systems inc. TPLink	not named as affected at publication, now names tapo c101 v5	Time to revision 139 days
Fri 14 Aug 2026· 1 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	Time to revision 238 days
Tue 11 Aug 2026· 1 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	Time to revision 15 days
Tue 4 Aug 2026· 1 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	Time to revision 175 days
Fri 31 Jul 2026· 1 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	Time to revision 179 days
Mon 13 Jul 2026· 2 changes
2026-07-13	Product added	CVE-2025-15608	tp-link systems inc. TPLink	not named as affected at publication, now names ax55 v4	Time to revision 115 days
2026-07-13	Product added	CVE-2025-15608	tp-link systems inc. TPLink	not named as affected at publication, now names ax55 v4.6	Time to revision 115 days
Thu 4 Jun 2026· 1 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	Time to revision 122 days
Wed 29 Apr 2026· 1 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	Time to revision 92 days
Thu 23 Apr 2026· 1 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	Time to revision 92 days
Wed 22 Apr 2026· 3 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	Time to revision 76 days
2026-04-22	Product added	CVE-2025-6982	tp-link systems inc. TPLink	not named as affected at publication, now names archer c20 v5	Time to revision 280 days
2026-04-22	Product added	CVE-2026-0834	tp-link systems inc. TPLink	not named as affected at publication, now names archer c20 v5	Time to revision 91 days
Fri 3 Apr 2026· 1 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	Time to revision 105 days
Thu 2 Apr 2026· 4 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	Time to revision 104 days
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	Time to revision 51 days
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	Time to revision 104 days
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	Time to revision 51 days
Thu 19 Mar 2026· 4 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	Time to revision 45 days
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	Time to revision 45 days
2026-03-19	Product added	CVE-2025-53711	tp link systems inc. TPLink	not named as affected at publication, now names tl-wr842nd v2	Time to revision 233 days
2026-03-19	Product added	CVE-2025-53711	tp link systems inc. TPLink	not named as affected at publication, now names tl-wr949n v3	Time to revision 233 days
Fri 13 Mar 2026· 2 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	Time to revision 31 days
2026-03-13	Product added	CVE-2026-0653	tp-link systems inc. TPLink	not named as affected at publication, now names tapo d235 v1	Time to revision 31 days
Mon 2 Mar 2026· 1 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	Time to revision 28 days
Mon 9 Feb 2026· 1 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	Time to revision 13 days
Tue 27 Jan 2026· 1 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	Time to revision 0 days
Wed 21 Jan 2026· 1 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	Time to revision 0 days
Fri 9 Jan 2026· 1 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	Time to revision 23 days
Wed 23 Jul 2025· 1 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	Time to revision 1 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.

4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

Every kind of change

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub advisory

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 →