dbcve.org
InjectionWeakness · CWE-74

CVE-2026-11406

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-06
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 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 · unedited
A vulnerability was determined in GL.iNet MT3000 up to 4.4.5. This vulnerability affects unknown code of the file ovpnclient.sh of the component OpenVPN Client Import Workflow. This manipulation causes command injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. Upgrading to version 4.9.0_beta3-1012-0513-1778656146 is able to resolve this issue. You should upgrade the affected component. The vendor confirms: "This issue has been addressed by implementing malicious checks on OpenVPN configuration files to prevent command injection attacks carried through malicious configuration files."

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 confidence

A command injection vulnerability exists in the GL.iNet MT3000 router firmware's OpenVPN client import functionality. Specifically, the ovpnclient.sh script does not properly validate or sanitize OpenVPN configuration files during import, allowing remote attackers to inject and execute arbitrary shell commands by uploading a maliciously crafted .ovpn configuration file.

MitigationUpgrade the GL.iNet MT3000 firmware to version 4.9.0_beta3-1012-0513-1778656146 or later, which implements validation checks on OpenVPN configuration files to block command injection attacks.

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

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
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? 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 checks

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

  1. Identify device model
    Check /proc/cpuinfo or the router's web interface for the device model to confirm it is a GL.iNet MT3000
    Affected if The device is a GL.iNet MT3000 router
  2. Check firmware version
    Look up the current firmware version in the router's admin panel (System > Firmware) or via command line (cat /etc/glversion), then compare it to the fixed version 4.9.0_beta3-1012-0513-1778656146
    Affected if The installed firmware version is lower than 4.9.0_beta3-1012-0513-1778656146
  3. Verify OpenVPN client import feature exists
    Check if the ovpnclient.sh script exists on the device by running: ls -la /etc/init.d/ovpnclient.sh or find / -name ovpnclient.sh 2>/dev/null
    Affected if The ovpnclient.sh script exists and the device is a vulnerable MT3000 model on an older firmware version

A user is affected if they are using a GL.iNet MT3000 router with firmware version lower than 4.9.0_beta3-1012-0513-1778656146 and the OpenVPN client import feature is present on the device.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the GL.iNet MT3000 firmware to version 4.9.0_beta3-1012-0513-1778656146 or later, which implements validation checks on OpenVPN configuration files to block command injection attacks.

Recommended fix High confidence

4.9.0_beta3-1012-0513-1778656146

  1. Download firmware version 4.9.0_beta3-1012-0513-1778656146 from the official GL.iNet support site (fw.gl-inet.cn)
  2. Back up the current router configuration
  3. Access the GL.iNet MT3000 admin interface
  4. Navigate to the firmware upgrade section
  5. Upload and apply the 4.9.0_beta3-1012-0513-1778656146 firmware file
  6. Allow the device to reboot and complete the upgrade process
  7. Verify the upgrade was successful by checking the firmware version in the admin panel
  8. After upgrade, the system will perform malicious checks on OpenVPN configuration files to prevent command injection attacks

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-11406 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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