InjectionWeakness · CWE-74

CVE-2026-11449

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-07

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

69/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

A security vulnerability has been detected in GL.iNet GL-MT3000 4.4.5. The impacted element is the function rpc_sys of the file /cgi-bin/luci/rpc of the component LuCI JSON-RPC Interface. Such manipulation leads to command injection. The attack may be performed from remote. Upgrading to version 4.8.1 is sufficient to resolve this issue. Upgrading the affected component is advised. The vendor confirms: "The issue discovered by the vulnerability researcher on older firmware versions(4.4.5) has actually been fixed and mitigated in the new version. According to the latest firmware fixes, by default, firmware versions after 4.7.13 do not install LuCI, so this vulnerability cannot be exploited."

Technical summary

dbcve analysis · high confidence

A command injection vulnerability exists in the LuCI JSON-RPC interface on GL.iNet GL-MT3000 firmware 4.4.5. The rpc_sys function in /cgi-bin/luci/rpc does not properly sanitize input, allowing an attacker to execute arbitrary commands remotely.

MitigationUpgrade the GL-MT3000 firmware to version 4.8.1 or later. Note that firmware versions after 4.7.13 do not install LuCI by default, which provides additional protection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify the router model

Check the device label or administrative interface for the model number to confirm it is a GL-MT3000

Affected if The device is not a GL-MT3000 router
Check the installed firmware version

Access the router admin panel or run 'gl-i' or check /etc/os-release to retrieve the firmware version

Affected if The firmware version is 4.4.5 (as specified in the CVE)
Verify LuCI is installed

Check if the LuCI web interface package exists on the device by attempting to access /cgi-bin/luci/ or checking for luci-app-* packages via the package manager

Affected if LuCI is installed and the /cgi-bin/luci/rpc endpoint is accessible
Confirm the RPC interface is reachable

Send a request to http://<router-ip>/cgi-bin/luci/rpc with a probe payload (e.g., an empty JSON object) to verify the endpoint responds

Affected if The RPC endpoint at /cgi-bin/luci/rpc returns a valid JSON-RPC response, indicating the vulnerable interface is active

You are affected if you have a GL-MT3000 router running firmware 4.4.5 with LuCI installed and the JSON-RPC interface at /cgi-bin/luci/rpc is accessible.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade the GL-MT3000 firmware to version 4.8.1 or later. Note that firmware versions after 4.7.13 do not install LuCI by default, which provides additional protection.

Recommended fix High confidence

4.8.1 or later

1. Log in to the GL-MT3000 web administration interface
2. Navigate to System > Firmware or System > Upgrade
3. Check the current firmware version to confirm it is 4.4.5 or another affected version
4. Download the firmware version 4.8.1 or later from the official GL.iNet support site (fw.gl-inet.com)
5. Upload the new firmware file through the web interface
6. Wait for the firmware upload and installation to complete; do not power off the device during this process
7. After reboot, log back into the administration interface
8. Verify the firmware has been updated to version 4.8.1 or later

Caveat Standard firmware upgrade risks apply; ensure stable power during upgrade to avoid device damage

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

7.0 hours of engineering $1,240

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-11449 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11449 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-11449?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 6.3 Medium

Exploit likelihood EPSS, next 30 days 1.1%

Remediation

Need this fixed?

Have this fixed 7 hrs · Low

Typical engagement from $1,240

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-11449 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References