CVE record · CVE-2026-12001

Hardcoded Credential Vulnerability in Multiple TP-Link Router Models

CVSS 5.2 MediumEPSS 0.0034 · 28th percentile

Published by the CVE Program (CNA: TPLink) at 27 Jul 2026, 20:08 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. TL-WR850N v3
  • affected before TL-WR850N(IN)_V3.48_3.16.0 Build 260422_2048 custom
Other versions: unaffected
TP-Link Systems Inc. Archer C20 v6
  • affected before Archer C20(US)_V6_250630 custom
Other versions: unaffected
TP Link Systems Inc. TL-WR845N v4
  • affected before TL-WR845N(UN)_V4_250401 custom
Other versions: unaffected
TP-Link Systems Inc. Archer MR200 v5
  • affected before EU_V5.20_1.3.0 Build 260319 custom
Other versions: unaffected
TP Link Systems Inc. TL-WR902AC v4
  • affected before US_V4_0.9.1 Build 260810 custom
  • affected before EU_V4_0.9.3 Build 260728 custom
Other versions: unaffected
Identifiers
CVE-2026-12001
CNA
TPLink
Weakness (CWE)
CWE-798
Published
27 Jul 2026
Updated
11 Aug 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.2 Medium 4.0 CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N CNA (TPLink)
  • CISA KEV Not listed.
  • EPSS 0.0034, the 28th percentile, on 11 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 27 Jul 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.