CVE-2026-9254

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 3.1% (87th 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

Also known asEUVD-2026-65006 (ENISA EUVD) · GHSA-3h97-6772-mpj4 (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
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: 3.1%CVSS: 8.7Exploit: 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).

An unauthenticated OS command injection vulnerability exists in the parental control functionality of Archer BE800 V1, BE3600 V1, and AX75 V1 due to improper filtering and neutralization of special characters in certain parameters. A LAN-based attacker can inject arbitrary commands and execute them with root privileges.

Successful exploitation may result in complete device compromise and impact the confidentiality, integrity, and availability of the affected device and network traffic.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation3.1% × 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
3.1%
EPSS %ILE
87th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
3.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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 13, 2026

Advisory Details (8)

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

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

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

다운로드 함 Archer BE3600 | TP-Link 대한민국

https://www.tp-link.com/kr/support/download/archer-be3600/v1/#Firmware

Vendor Advisories for CVE-2026-9254(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 10× in last 7d / 65× 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 204 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 105 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-9254?
CVE-2026-9254 is a high-severity vulnerability; its CVE record was published on August 24, 2026. An unauthenticated OS command injection vulnerability exists in the parental control functionality of Archer BE800 V1, BE3600 V1, and AX75 V1 due to improper filtering and neutralization of special characters in certain parameters. A LAN-based attacker can inject arbitrary commands and execute them…
When was the CVE record for CVE-2026-9254 published?
The CVE record for CVE-2026-9254 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 13, 2026; the record at its source may have been updated since.
Is CVE-2026-9254 actively exploited?
CVE-2026-9254 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% probability of exploitation in the next 30 days (87th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9254?
CVE-2026-9254 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-9254?
A fix for CVE-2026-9254 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-9254 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-9254?

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