InjectionWeakness · CWE-74

CVE-2026-11450

HIGH · 7.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 →

82/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

A vulnerability was detected in GL.iNet GL-MT3000 4.4.5. This affects the function dlopen in the library /usr/lib/oui-httpd/rpc/ of the component Path Normalization Handler. Performing a manipulation of the argument dev_name results in command injection. It is possible to initiate the attack remotely. Upgrading to version 4.7 mitigates this issue. It is advisable to upgrade the affected component. The vendor confirms: " From version 4.7 onward, we have enabled method‑level validation at the HTTP /rpc layer. nas‑web.eject_disk is no longer in the whitelist of allowed methods. Consequently, directly calling eject_disk through the default /rpc endpoint returns Invalid params, preventing entry into subsequent dangerous functions and blocking the remote exploit chain described in the report."

Technical summary

dbcve analysis · high confidence

Command injection vulnerability in GL.iNet GL-MT3000 router firmware 4.4.5 allows remote attackers to execute arbitrary commands via the dlopen function in the /usr/lib/oui-httpd/rpc/ component by manipulating the dev_name argument in the Path Normalization Handler.

MitigationUpgrade GL-MT3000 firmware to version 4.7 or later, which implements method-level validation at the HTTP /rpc layer and removes the vulnerable nas-web.eject_disk method from the whitelist.

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: None
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

CVSS:3.1/AV:N/AC:L/PR:N/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 GL-MT3000 firmware version

Access the router admin interface and navigate to System > Firmware, or use the command line: cat /etc/os-release or gl-ar300m 2>/dev/null to retrieve the installed firmware version

Affected if The firmware version is below 4.7 (e.g., 4.6.x or earlier)
Verify the /rpc endpoint exists

Check for the presence of the /rpc endpoint directory by examining the web server configuration or attempting to access https://<router-ip>/rpc on the device

Affected if The /rpc endpoint is accessible and responds to requests
Confirm nas-web.eject_disk method presence

Examine the allowed methods whitelist configuration file in /usr/lib/oui-httpd/rpc/ or the HTTP daemon configuration to see if nas-web.eject_disk is listed as an permitted method

Affected if The nas-web.eject_disk method is present in the method whitelist
Check for the vulnerable Path Normalization Handler library

Inspect the file /usr/lib/oui-httpd/rpc/ on the device to verify the Path Normalization Handler library exists

Affected if The library file at /usr/lib/oui-httpd/rpc/ is present and executable

The device is affected if running firmware version below 4.7 AND the nas-web.eject_disk method remains in the allowed methods whitelist accessible via the /rpc endpoint.

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 GL-MT3000 firmware to version 4.7 or later, which implements method-level validation at the HTTP /rpc layer and removes the vulnerable nas-web.eject_disk method from the whitelist.

Recommended fix High confidence

GL.iNet GL-MT3000 firmware version 4.7

Download the firmware version 4.7 or later from the official GL.iNet support portal for the GL-MT3000 device
Access the router's web administration interface
Navigate to the Firmware Upgrade or System settings section
Upload and install the version 4.7 firmware file
After reboot, verify the upgrade was successful and the /rpc endpoint no longer accepts the eject_disk method

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

Have this fixed Scoped from the published advisory

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

6.0 hours of engineering $1,060

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-11450 — 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-11450 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-11450?

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 7.3 High

Exploit likelihood EPSS, next 30 days 1.6%

Remediation

A high-priority fix

Have this fixed 6 hrs · Low

Typical engagement from $1,060

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-11450 and return a fixed quote and timeline.

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