CVE-2026-26795
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 · uneditedGL-iNet GL-AR300M16 v4.3.11 was discovered to contain a command injection vulnerability via the module parameter in the M.get_system_log function. This vulnerability allows attackers to execute arbitrary commands via a crafted input.
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 analysis · high confidenceA command injection vulnerability exists in the GL-iNet GL-AR300M16 router firmware v4.3.11. The vulnerability is in the M.get_system_log function where the module parameter is not properly sanitized before being used in system command execution, allowing unauthenticated attackers to inject and execute arbitrary operating system commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.3.11CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify firmware version via web interfaceLog into the router web UI (typically 192.168.1.1), navigate to System > Firmware or System > About, and locate the firmware version displayed. Confirm it shows exactly version 4.3.11.Affected if The displayed firmware version is 4.3.11
-
Identify firmware version via CLIAccess the router via SSH or serial console and run: cat /etc/os-release or cat /etc/glversion (GL-iNet specific). Check the VERSION or FIRMWARE field for 4.3.11.Affected if The command output shows firmware version 4.3.11
-
Verify the web API endpoint existsCheck if the /cgi-bin/luci/api/system or similar GL-iNet API endpoint is accessible. This can be done by attempting a curl request to the router's web API. The vulnerable function is M.get_system_log in the system module.Affected if The router web interface is reachable and responds to API requests
-
Confirm the module parameter is not sanitizedThis requires examining the Lua source code or testing. The vulnerability lies in the M.get_system_log function where user-supplied input to the module parameter is passed directly to a system() call without sanitization. If you can access the router filesystem (via SSH or by extracting firmware), inspect the Lua scripts in /usr/lib/lua/ for the get_system_log function.Affected if The module parameter accepts and processes unsanitized input passed to shell commands
A user is affected if they are running GL-AR300M16 firmware exactly version 4.3.11 and the web interface with the M.get_system_log API endpoint is accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched firmware version if available. If no update exists, implement input validation and sanitization on the module parameter in the affected function, or deploy a web application firewall to block malicious requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26795 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26795 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
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
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