CVE-2026-78541

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 2.3% (82nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
8.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.3%CVSS: 8.5Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

A stored OS command injection vulnerability exists in the parent-control module of TP-Link Archer BE3600 V1. An authenticated adjacent attacker with administrative access may store a crafted profile name containing shell metacharacters, which is later processed unsafely during daily cloud report generation and may result in arbitrary command execution.

Successful exploitation may allow command execution on the affected device with potential impact to device confidentiality, integrity, and availability.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity85% × 45%
The EG Score, 8.5 of 10.
Exploitation2.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
2.3%
EPSS %ILE
82nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 24, 2026

Last Modified

October 12, 2026

Advisory Details (3)

Auto-updated Aug 24, 2026
Fix referenced — no release confirmed yet.
Web page

Security Advisory: Multiple Command Injection Vulnerabilities in Archer Products (CVE-2026-9254, CVE-2026-16348, CVE-2026-78541) | TP-Link

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

Vendor Advisories for CVE-2026-78541(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 99× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 182 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 83 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  3. 2026-10-12 15:26 UTCEG score recompute
  4. 2026-10-12 15:26 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  5. 2026-10-11 19:22 UTCEG score recompute
  6. 2026-10-11 16:38 UTCEG score recompute
  7. 2026-10-11 13:57 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  10. 2026-10-10 12:33 UTCEG score recompute
  11. 2026-10-10 12:32 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  13. 2026-10-09 04:46 UTCEG score recompute
  14. 2026-10-09 04:46 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  15. 2026-10-08 17:13 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  16. 2026-10-08 03:50 UTCEG score recompute
  17. 2026-10-08 03:50 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  19. 2026-10-07 04:22 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  20. 2026-10-06 16:10 UTCEG score recompute
  21. 2026-10-06 16:10 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  22. 2026-10-06 15:18 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  23. 2026-10-06 02:47 UTCEG score recompute
  24. 2026-10-06 02:47 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  25. 2026-10-05 17:43 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
Show 74 more
  1. 2026-10-05 09:21 UTCEG score recompute
  2. 2026-10-05 09:21 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  3. 2026-10-04 23:22 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  4. 2026-10-04 20:41 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  5. 2026-10-04 04:54 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  6. 2026-10-03 16:31 UTCEG score recompute
  7. 2026-10-03 16:31 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  8. 2026-10-03 14:26 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  9. 2026-10-02 21:33 UTCEG score recompute
  10. 2026-10-02 21:33 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  11. 2026-10-02 09:12 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  12. 2026-10-01 21:02 UTCEG score recompute
  13. 2026-10-01 21:02 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  14. 2026-10-01 19:50 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  15. 2026-10-01 08:28 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  16. 2026-09-30 20:17 UTCEG score recompute
  17. 2026-09-30 20:17 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  18. 2026-09-30 07:00 UTCEG score recompute
  19. 2026-09-30 07:00 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  20. 2026-09-29 15:24 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  21. 2026-09-29 15:08 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  22. 2026-09-29 01:39 UTCEG score recompute
  23. 2026-09-29 01:39 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  24. 2026-09-28 13:52 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  25. 2026-09-28 12:35 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  26. 2026-09-28 00:25 UTCEG score recompute
  27. 2026-09-28 00:25 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  28. 2026-09-27 13:48 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  29. 2026-09-27 12:14 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  30. 2026-09-27 00:03 UTCEG score recompute
  31. 2026-09-27 00:03 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  32. 2026-09-26 15:59 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  33. 2026-09-26 00:28 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  34. 2026-09-25 12:37 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  35. 2026-09-25 00:26 UTCEG score recompute
  36. 2026-09-25 00:26 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  37. 2026-09-24 14:04 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  38. 2026-09-24 12:14 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  39. 2026-09-24 00:03 UTCEG score recompute
  40. 2026-09-24 00:03 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  41. 2026-09-23 17:54 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  42. 2026-09-23 11:52 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  43. 2026-09-22 23:41 UTCEG score recompute
  44. 2026-09-22 23:41 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  45. 2026-09-22 16:01 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  46. 2026-09-22 11:25 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  47. 2026-09-21 23:14 UTCEG score recompute
  48. 2026-09-21 23:14 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  49. 2026-09-21 21:09 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  50. 2026-09-21 11:03 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  51. 2026-09-20 22:53 UTCEG score recompute
  52. 2026-09-20 22:53 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  53. 2026-09-20 20:16 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  54. 2026-09-20 10:42 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  55. 2026-09-19 22:29 UTCEG score recompute
  56. 2026-09-19 22:29 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  57. 2026-09-19 10:07 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  58. 2026-09-18 21:34 UTCEG score recompute
  59. 2026-09-18 21:34 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  60. 2026-09-18 19:28 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  61. 2026-09-18 09:23 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  62. 2026-09-17 21:11 UTCEG score recompute
  63. 2026-09-17 21:11 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  64. 2026-09-17 07:43 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  65. 2026-09-16 19:30 UTCEG score recompute
  66. 2026-09-16 19:30 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  67. 2026-09-16 14:08 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  68. 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  69. 2026-09-16 04:36 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  70. 2026-09-15 16:12 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  71. 2026-09-15 04:01 UTCEG score recompute
  72. 2026-09-15 04:01 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH
  73. 2026-09-15 03:12 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  74. 2026-09-14 15:49 UTCGHSA enrichmentGHSA-3p5q-gg9q-4336 · GitHub severity HIGH

Frequently asked(5)

What is CVE-2026-78541?
CVE-2026-78541 is a high-severity vulnerability; its CVE record was published on August 24, 2026. A stored OS command injection vulnerability exists in the parent-control module of TP-Link Archer BE3600 V1. An authenticated adjacent attacker with administrative access may store a crafted profile name containing shell metacharacters, which is later processed unsafely during daily cloud report…
When was the CVE record for CVE-2026-78541 published?
The CVE record for CVE-2026-78541 was published on August 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-78541 actively exploited?
CVE-2026-78541 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.3% probability of exploitation in the next 30 days (82nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78541?
CVE-2026-78541 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-78541?
A fix for CVE-2026-78541 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-78541 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-78541?

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