A weakness has been identified in GL.iNet A1300, AX1800, AXT1800, BE1400, BE3600, BE6500, BE9300, BE10000, E5800, MT2500, MT3000, MT3600BE, MT5000, MT6000, X2000, X3000 and XE3000 up to 4.8.x. This affects an unknown part of the component Wi-Fi Timer Power-Schedule Feature. Executing a manipulation of the argument switch_power/restore_power can lead to os command injection. The attack can be launched remotely. The vendor explains: "After our investigation, we have confirmed that the vulnerability described (...) does indeed exist."
CVE-2026-19981
Score 7.4 from GitHub Security Advisory published 2026-08-17. a secondary CVSS source baseline 7.4; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.4
- EG Score
- 7.4(high)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
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 computedSeverity74% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 62%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 20, 2026
Advisory Details (1)
Auto-updated Aug 17, 2026CVE-issues/4.0.0/Wi-Fi Timer Power-Schedule Cron RCE.md at main · gl-inet/CVE-issues · GitHub
https://github.com/gl-inet/CVE-issues/blob/main/4.0.0/Wi-Fi%20Timer%20Power-Schedule%20Cron%20RCE.mdVendor Advisories for CVE-2026-19981(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 23× in last 7d / 23× 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.
- 2026-08-20 23:49 UTCEG score recompute
- 2026-08-20 23:49 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 13:00 UTCGHSA enrichment
- 2026-08-20 10:14 UTCGHSA enrichment
- 2026-08-19 23:25 UTCEG score recompute
- 2026-08-19 23:25 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 12:35 UTCGHSA enrichment
- 2026-08-19 01:46 UTCGHSA enrichment
- 2026-08-18 14:56 UTCEG score recompute
- 2026-08-18 14:56 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 03:10 UTCEG score recompute
- 2026-08-18 03:10 UTCGHSA enrichment
- 2026-08-17 16:17 UTCEG score recompute
- 2026-08-17 16:17 UTCGHSA enrichment
- 2026-08-17 15:18 UTCEG score recompute
- 2026-08-17 15:18 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 04:29 UTCEG score recompute
- 2026-08-17 04:15 UTCEG score recompute
- 2026-08-17 04:14 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
- CVE-2011-0271EG 10.0EPSS p94HIGH
- CVE-2010-3757EG 10.0EPSS p90HIGH
- CVE-2010-3754EG 10.0EPSS p91HIGH
Frequently asked(5)
What is CVE-2026-19981?
When was CVE-2026-19981 disclosed?
Is CVE-2026-19981 actively exploited?
What is the CVSS score of CVE-2026-19981?
How do I remediate CVE-2026-19981?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-19981
Is Your Infrastructure Affected by CVE-2026-19981?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.