CVE-2026-3227

MEDIUMNVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-16. NVD baseline CVSS 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
6.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.8
EG Score
6.8(medium)
EPSS
62.0%
KEV
Not listed

Published

March 16, 2026

Last Modified

July 1, 2026

Advisory Details (3)

Auto-updated Jul 1, 2026
No patch confirmed yet.
generic

Security Advisory on Authenticated Command Injection Vulnerability on TP-Link TL-WR802N, TL-WR841N and TL-WR840N (CVE-2026-3227)

https://www.tp-link.com/us/support/faq/5018/
generic

Download for TL-WR840N | TP-Link

https://www.tp-link.com/en/support/download/tl-wr840n/v6/#Firmware
generic

Download for TL-WR802N | TP-Link

https://www.tp-link.com/en/support/download/tl-wr802n/v4/#Firmware

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-13 22:30 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-08 15:15 UTCEPSS rescore
  11. 2026-07-07 13:46 UTCEPSS rescore
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 13:49 UTCEPSS rescore
Show 67 more
  1. 2026-06-24 14:05 UTCEPSS rescore
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-22 14:25 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 14:56 UTCEPSS rescore
  7. 2026-06-21 01:59 UTCEPSS rescore
  8. 2026-06-19 19:25 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-18 17:52 UTCEPSS rescore
  11. 2026-06-17 17:53 UTCEPSS rescore
  12. 2026-06-16 17:52 UTCEPSS rescore
  13. 2026-06-15 17:49 UTCEPSS rescore
  14. 2026-06-14 23:18 UTCEPSS rescore
  15. 2026-06-13 23:00 UTCEPSS rescore
  16. 2026-06-12 23:12 UTCEPSS rescore
  17. 2026-06-12 23:12 UTCEPSS rescore
  18. 2026-06-11 23:59 UTCEG score recompute
  19. 2026-06-11 23:59 UTCGHSA enrichment
  20. 2026-06-11 14:00 UTCEPSS rescore
  21. 2026-06-10 22:18 UTCEPSS rescore
  22. 2026-06-10 15:51 UTCEG score recompute
  23. 2026-06-10 15:51 UTCGHSA enrichment
  24. 2026-06-10 13:22 UTCEPSS rescore
  25. 2026-06-09 16:44 UTCEG score recompute
  26. 2026-06-09 16:44 UTCGHSA enrichment
  27. 2026-06-08 14:17 UTCEPSS rescore
  28. 2026-06-08 14:17 UTCEPSS rescore
  29. 2026-06-07 15:25 UTCEPSS rescore
  30. 2026-06-07 15:25 UTCEPSS rescore
  31. 2026-06-07 15:25 UTCEPSS rescore
  32. 2026-06-07 14:37 UTCEG score recompute
  33. 2026-06-07 14:37 UTCGHSA enrichment
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-06 13:47 UTCEPSS rescore
  36. 2026-06-05 22:47 UTCEPSS rescore
  37. 2026-06-05 22:47 UTCEPSS rescore
  38. 2026-06-05 06:10 UTCEPSS rescore
  39. 2026-06-05 06:10 UTCEPSS rescore
  40. 2026-06-04 13:12 UTCEPSS rescore
  41. 2026-06-04 13:12 UTCEPSS rescore
  42. 2026-06-02 20:13 UTCEPSS rescore
  43. 2026-06-01 13:52 UTCEPSS rescore
  44. 2026-06-01 13:52 UTCEPSS rescore
  45. 2026-06-01 13:51 UTCEPSS rescore
  46. 2026-05-31 22:30 UTCEPSS rescore
  47. 2026-05-31 22:30 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-31 00:16 UTCEPSS rescore
  50. 2026-05-31 00:16 UTCEPSS rescore
  51. 2026-05-29 13:44 UTCEPSS rescore
  52. 2026-05-29 13:44 UTCEPSS rescore
  53. 2026-05-28 13:44 UTCEPSS rescore
  54. 2026-05-28 13:44 UTCEPSS rescore
  55. 2026-05-28 13:44 UTCEPSS rescore
  56. 2026-05-27 13:40 UTCEPSS rescore
  57. 2026-05-27 13:40 UTCEPSS rescore
  58. 2026-05-27 13:40 UTCEPSS rescore
  59. 2026-05-26 13:44 UTCEPSS rescore
  60. 2026-05-26 07:18 UTCEPSS rescore
  61. 2026-05-26 07:18 UTCEPSS rescore
  62. 2026-05-20 22:38 UTCEPSS rescore
  63. 2026-05-20 22:38 UTCEPSS rescore
  64. 2026-05-20 21:08 UTCEG score recompute
  65. 2026-05-20 21:08 UTCGHSA enrichment
  66. 2026-05-20 11:22 UTCEPSS rescore
  67. 2026-05-20 11:22 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCdo4choo/CVE-2026-3227
    First seen Jun 25, 2026
    Open source ↗
  • GitHub PoCdo4choo/CVE-2026-3227-TP-Link-authenticated-RCE
    First seen Jun 25, 2026
    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-3227?
CVE-2026-3227 is a medium vulnerability published on March 16, 2026. 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…
When was CVE-2026-3227 disclosed?
CVE-2026-3227 was first published in the National Vulnerability Database on March 16, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3227 actively exploited?
CVE-2026-3227 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 62.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-3227?
CVE-2026-3227 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-3227?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3227, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-3227

Explore →

Is Your Infrastructure Affected by CVE-2026-3227?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs