CVE record · CVE-2025-15551

LAN Code Execution on TP-Link Archer MR200, Archer C20, TL-WR850N and TL-WR845N

CVSS 5.9 MediumEPSS 0.0044 · 38th percentile

Published by the CVE Program (CNA: TPLink) at 5 Feb 2026, 17:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

Affected products, as the CNA wrote them
VendorProductVersions
TP-Link Systems Inc. Archer MR200 v5.2
  • affected before 1.2.0 Build 250917 Rel.51746 custom
Other versions: unaffected
TP-Link Systems Inc. Archer C20 v6
  • affected before 0.9.1 4.19 v0001.0 Build 250630 Rel.56583n custom
Other versions: unaffected
TP Link Systems Inc. TL-WR850N v3
  • affected before 3.16.0 0.9.1 v6031.0 Build 251205 Rel.22089n custom
Other versions: unaffected
TP Link Systems Inc. TL-WR845N v4
  • affected before 0.9.1 3.19 Build 251031 rel33710 custom
Other versions: unaffected
TP-Link Systems Inc. Archer C20 v5
  • affected before US_V5_260419 custom
  • affected before EU_V5_260317 custom
Other versions: unaffected
Identifiers
CVE-2025-15551
CNA
TPLink
Weakness (CWE)
CWE-95
Published
5 Feb 2026
Updated
22 Apr 2026

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.9 Medium 4.0 CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N CNA (TPLink)
  • CISA KEV Not listed.
  • EPSS 0.0044, the 38th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the CVE Program, published 5 Feb 2026. New records show when each source confirmed them.

Sources

References from the CNA

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.