CVE-2026-79911

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-26. A secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
10.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

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

A security vulnerability has been detected in TOTOLINK N600R 4.3.0cu.7647_B20210106. The affected element is the function setSystemConfig of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. Such manipulation of the argument Hostname leads to stack-based buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.1%
EPSS %ILE
64th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 25, 2026

Last Modified

August 27, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
No fix on record yet.
Web page

TOTOLINK | Wi-Fi 7, Mesh, 5G & Enterprise Networking

https://www.totolink.net/
Web page

iot-overflow/TOTOLINK_N600R_cstecgi_strcpy_sprintf_Multi_Function_Stack_Overflow.md at main · dxz0069/iot-overflow · GitHub

https://github.com/dxz0069/WAVLINK-WN530H4-Command-Injection-in-set_add_routing/blob/main/TOTOLINK_N600R_cstecgi_strcpy_sprintf_Multi_Function_Stack_Overflow.md

Vendor Advisories for CVE-2026-79911(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 178× 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 100 of 324 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. None are among the latest 100 rows. The 224 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-79911?
CVE-2026-79911 is a critical-severity vulnerability; its CVE record was published on August 25, 2026. A security vulnerability has been detected in TOTOLINK N600R 4.3.0cu.7647_B20210106. The affected element is the function setSystemConfig of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. Such manipulation of the argument Hostname leads to stack-based buffer overflow. It is possible to…
When was the CVE record for CVE-2026-79911 published?
The CVE record for CVE-2026-79911 was published on August 25, 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 August 27, 2026; the record at its source may have been updated since.
Is CVE-2026-79911 actively exploited?
CVE-2026-79911 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79911?
CVE-2026-79911 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-79911?
No fix for CVE-2026-79911 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-79911 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-79911?

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

Book a Demo →Browse All CVEs