Product added
| 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 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 | CVE-2026-15315 | 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 | CVE-2026-12339 | TPLink | not named as affected at publication, now names tl-mr100 v3.20 | Days to revision 15 |
| 2026-08-25 | CVE-2026-12339 | TPLink | not named as affected at publication, now names tl-mr150 v3.20 | Days to revision 15 |
| 2026-08-25 | CVE-2026-12339 | 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 | CVE-2026-34118 | TPLink | not named as affected at publication, now names tapo c100 v5 | Days to revision 139 |
| 2026-08-19 | CVE-2026-34118 | 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 | CVE-2025-14300 | 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 | CVE-2026-12001 | 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 | CVE-2026-0651 | 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 | CVE-2026-0631 | 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 | CVE-2025-15608 | TPLink | not named as affected at publication, now names ax55 v4 | Days to revision 115 |
| 2026-07-13 | CVE-2025-15608 | 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 | CVE-2026-22226 | 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 | CVE-2026-0919 | 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 | CVE-2026-0834 | 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 | CVE-2025-15551 | TPLink | not named as affected at publication, now names archer c20 v5 | Days to revision 76 |
| 2026-04-22 | CVE-2025-6982 | TPLink | not named as affected at publication, now names archer c20 v5 | Days to revision 280 |
| 2026-04-22 | CVE-2026-0834 | 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 | CVE-2025-14300 | TPLink | not named as affected at publication, now names tapo c100 v5 | Days to revision 105 |
| Thu 2 Apr 2026· 2 record changes | ||||
| 2026-04-02 | CVE-2025-8065 | TPLink | not named as affected at publication, now names tapo c520ws v2.6 | Days to revision 104 |
| 2026-04-02 | CVE-2026-0651 | TPLink | not named as affected at publication, now names tapo c520ws v2.6 | Days to revision 51 |
| Thu 19 Mar 2026· 4 record changes | ||||
| 2026-03-19 | CVE-2026-0630 | TPLink | not named as affected at publication, now names axe75 v1.0 | Days to revision 45 |
| 2026-03-19 | CVE-2026-22225 | TPLink | not named as affected at publication, now names archer ax53 v1.0 | Days to revision 45 |
| 2026-03-19 | CVE-2025-53711 | TPLink | not named as affected at publication, now names tl-wr842nd v2 | Days to revision 233 |
| 2026-03-19 | CVE-2025-53711 | 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 | CVE-2026-0651 | TPLink | not named as affected at publication, now names tapo d235 v1 | Days to revision 31 |
| 2026-03-13 | CVE-2026-0653 | 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 | CVE-2026-22229 | 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 | CVE-2026-0918 | TPLink | not named as affected at publication, now names tapo c100 v5 | Days to revision 13 |
| Fri 9 Jan 2026· 1 record change | ||||
| 2026-01-09 | CVE-2025-14553 | TPLink | not named as affected at publication, now names tp-link tapo app | Days to revision 23 |
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.
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 →