CVE-2026-15469
CVE-2026-15469 — Hard-coded Mesh Group Private Key in TP-Link Deco XE75, XE5300, and WE10800
The use of hard-coded cryptographic key vulnerability has been identified in the mesh functionality of Deco XE75 v3, XE5300 v3.6 and WE10800 v3.6. A shared RSA-512 mesh group private key is present in the affected firmware and is used by the mesh protocol for node authentication. An attacker who obtains the firmware image and has local network access may be able to authenticate as a mesh node without possessing a device-specific credential. Successful exploitation may allow an unauthenticated adjacent attacker to impersonate a trusted mesh node and bypass mesh node authentication, which may permit unauthorized changes to device or mesh configuration, affecting confidentiality, integrity and availability.
Published Updated Sources: NVD, TP-Link Systems Inc. (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Reported
not confirmed by CISA
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
7.7
high
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
Upgrade Deco XE75 v3 / XE5300 v3.6/ WE10800 v3.6 to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| TP-Link Systems Inc. | Deco XE75 v3 / XE5300 v3.6/ WE10800 v3.6 | 0 to < 1.5.0 Build 20260603 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Scope
X
Attack Complexity
Low
Attack Vector
Adjacent
Privileges Req
None
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.7 | CVSS 4.0 | high | — | — | TP-Link Systems Inc. (CNA) |
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-321 · Use of Hard-coded Cryptographic Key
- Bypass Protection Mechanism
- Gain Privileges or Assume Identity
Mitigation: Prevention schemes mirror that of hard-coded password storage.::
Weakness & attack patterns
- CWE-321
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
5
2 of the 5 sampled are weaponized
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Monitor for scanner or exploit-pattern traffic after 5 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 7.7 (AV:A)
Aug 24, 2026 · NVD
Initial · CVE published
Aug 24, 2026 · NVD
Added · GHSA-w7r2-cxjq-9w33 published (high)
Aug 24, 2026 · GitHub Security Advisory
Source activity
Readings a source repeats on a schedule, counted rather than listed.
- 1×CVE modified by NIST, Modified, LinkAug 24, 2026 · SOCRadar CTI
References
11 on the record
- www.tp-link.com/en/support/download/deco-xe75/v3.60/#Firmware
Vendor Advisory
- www.tp-link.com/us/support/download/deco-we10800/#Firmware
Vendor Advisory
- www.tp-link.com/us/support/download/deco-xe5300/#Firmware
Vendor Advisory
- www.tp-link.com/us/support/download/deco-xe75/v3.60/#Firmware
Vendor Advisory
- www.tp-link.com/us/support/faq/5263/
Vendor Advisory, NIST
- nvd.nist.gov/vuln/detail/CVE-2026-15469
NVD
- github.com/advisories/GHSA-w7r2-cxjq-9w33
Exploit, Third Party Advisory
- www.tp-link.com/en/support/download/deco-xe75/v3.60/%23Firmware
NIST
Elsewhere on this site
- TP-Link Systems Inc.every CVE for this vendor
- Unclassifiedsame class
- CWE-321other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-15469 is Hard-coded Mesh Group Private Key in TP-Link Deco XE75, XE5300, and WE10800, a high vulnerability affecting Deco XE75 v3 / XE5300 v3.6/ WE10800 v3.6 from TP-Link Systems Inc.. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: 5 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.7 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.