CVE-2026-19981 is command injection in GL.iNet's power scheduling feature, affecting 17 models from the A1300 through the BE10000—a span suggesting the same architectural pattern persisted across 6-8 years of product development. The analytically significant dimension isn't the injection itself; it's that this vulnerability lives in a feature users interact with regularly, embedded in scheduled execution. This changes the threat model fundamentally: exploitation isn't a one-time event but a persistent foothold. An attacker injects commands into the schedule, and they fire every night at the configured time, surviving reboots and blending into normal device behavior. The CVSS 7.4 captures a single injection event—it does not model a persistent execution environment inside your network. Prioritize determining whether the power scheduling interface is accessible pre-authentication or requires authenticated access, since this determines whether this is initial access or privilege escalation. Examine the switch_power/restore_power argument handling to understand the exact parsing failure—variable expansion, command chaining, or direct shell passthrough. More critically, verify whether GL.iNet's fix addresses the architectural pattern (UI input reaching shell) or merely sanitizes the specific arguments; argument-level sanitization in shell-mediated code is notoriously brittle. Treat scheduled execution as a monitoring surface: power schedules fire at known times with known parameters, creating detection opportunities that most security tooling ignores because power scheduling has been relegated to "forgotten infrastructure." This vulnerability class—shell-as-integration-layer in consumer IoT convenience features—has appeared repeatedly across Linksys, Netgear, and TP-Link. The pattern is documented; the recurrence suggests the development workflow isn't connecting to that documentation.
CVE-2026-19981
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisUser input reaches a command interpreter without being fully separated from the command itself, so an attacker can append instructions of their own. Because those run with the application's privileges, it frequently means control of the host. The lasting fix is to avoid constructing commands from input — call APIs directly and pass arguments as data, never as concatenated strings.
General guidance for the command injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $8,000. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-19981 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesCVE-2026-19981 is command injection in GL.iNet's power scheduling feature, affecting 17 models from the A1300 through the BE10000—a span suggesting the same architectural pattern persisted across 6-8 years of product development. The analytically significant dimension isn't the injection itself; it's that this vulnerability lives in a feature users interact with regularly, embedded in scheduled execution. This changes the threat model fundamentally: exploitation isn't a one-time event but a persistent foothold. An attacker injects commands into the schedule, and they fire every night at the configured time, surviving reboots and blending into normal device behavior. The CVSS 7.4 captures a single injection event—it does not model a persistent execution environment inside your network. Prioritize determining whether the power scheduling interface is accessible pre-authentication or requires authenticated access, since this determines whether this is initial access or privilege escalation. Examine the switch_power/restore_power argument handling to understand the exact parsing failure—variable expansion, command chaining, or direct shell passthrough. More critically, verify whether GL.iNet's fix addresses the architectural pattern (UI input reaching shell) or merely sanitizes the specific arguments; argument-level sanitization in shell-mediated code is notoriously brittle. Treat scheduled execution as a monitoring surface: power schedules fire at known times with known parameters, creating detection opportunities that most security tooling ignores because power scheduling has been relegated to "forgotten infrastructure." This vulnerability class—shell-as-integration-layer in consumer IoT convenience features—has appeared repeatedly across Linksys, Netgear, and TP-Link. The pattern is documented; the recurrence suggests the development workflow isn't connecting to that documentation.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-19981 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data