CVE-2026-3227 — Authenticated Command Injection on TP-Link TL-WR802N, TL-WR841N and TL-WR840N
A command injection vulnerability was identified in TP-Link TL-WR802N v4, TL-WR841N v14, and TL-WR840N v6 due to improper neutralization of special elements used in an OS command. In the router configuration import function allows an authenticated attacker to upload a crafted configuration file that results in execution of OS commands with root privileges during port-trigger processing. Successful exploitation allows an authenticated attacker to execute system commands with root privileges, leading to full device compromise.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 1.9% (30-day exploitation probability)+12
- Technical severity (medium)+3
- CISA SSVC: exploitation "poc"+5
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (TP-Link Systems Inc. Tl-wr802n Firmware, TP-Link Systems Inc. TL-WR802N v4, TP-Link Systems Inc. Tl-wr840n Firmware…).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| TP-Link Systems Inc. | Tl-wr802n Firmware | < 260304 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | TL-WR802N v4 | < V4_260304 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| TP-Link Systems Inc. | Tl-wr840n Firmware | < 260304 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | TL-WR840N v6 | < V6_260304 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| TP-Link Systems Inc. | Tl-wr841n Firmware | < 260303 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | TL-WR841N v14 | < V14_260303 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.5 | CVSS 4.0 | High | — | — | f23511db-6c3e-4e32-a477-6aa17d310630 via NIST National Vulnerability Database |
| 8.5 | CVSS 4.0 | High | — | — | TPLink via CVE Program (cve.org) e CISA ADP |
| 6.8 | CVSS 3.1 | Medium | 0.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.88%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · tp-link systems inc./tl-wr802n v4, tp-link systems inc./tl-wr841n v14, tp link systems inc./tl-wr840n v6
- SSVC assessment updated
- Record published
- CVSS changed · 6.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
6 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-9105 Authenticated Stack-Based Buffer Overflow in TP-Link TL-WR841N Web Interface Jun 29, 2026
- High CVE-2026-5039 Predictable Default Cryptographic Key Used for DES Encryption in TP-Link TL-WL841N Apr 23, 2026
- High CVE-2026-3622 Denial-of-Service Vulnerability in UPnP Component of TP Link's TL-WR841N Mar 26, 2026
- High CVE-2025-9014 Null Pointer Dereference Vulnerability on TL-WR841N Jan 15, 2026
- High CVE-2025-9377 TP-Link Archer C7(EU) and TL-WR841N/ND(MS) OS Command Injection Vulnerability KEV Aug 29, 2025
- Medium CVE-2023-50224 TP-Link TL-WR841N Authentication Bypass by Spoofing Vulnerability KEV May 3, 2024
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 fixed version, patch or mitigation documented.
- 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 record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-3227 is "Authenticated Command Injection on TP-Link TL-WR802N, TL-WR841N and TL-WR840N", rated Medium. It affects Tl-wr802n Firmware (TP-Link Systems Inc.); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.8 describes technical severity. EPSS 1.88% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.