dbcve.org
InjectionWeakness · CWE-74

CVE-2026-12187

HIGH · 8.8 CVSS v3.1 Published 2026-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 security vulnerability has been detected in GL.iNet GL-MT3000 up to 4.4.5. Affected by this vulnerability is an unknown functionality of the file /usr/bin/one_click_upgrade of the component Online Firmware Upgrade Handler. Such manipulation leads to command injection. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 4.7 addresses this issue. Upgrading the affected component is advised. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

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

Command injection vulnerability in the /usr/bin/one_click_upgrade component of GL.iNet GL-MT3000 routers running firmware up to version 4.4.5 allows remote attackers to execute arbitrary commands via manipulated inputs to the Online Firmware Upgrade Handler.

MitigationUpgrade GL-MT3000 firmware to version 4.7 or later to remediate this command injection vulnerability.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Confirm router model is GL-MT3000
    Access the router admin panel (typically at 192.168.8.1) and check the device model under System > Overview or the status page. Alternatively, check the physical device label or use the command 'cat /proc/cpuinfo' via SSH if available.
    Affected if The device is not a GL-MT3000 router, then this specific CVE does not apply.
  2. Identify installed firmware version
    In the router admin panel, navigate to System > Firmware Upgrade or System > Overview to find the current firmware version. Alternatively, run 'cat /etc/os-release' or 'cat /proc/version' via SSH to retrieve the version string.
    Affected if The installed firmware version is 4.4.5 or earlier, indicating the vulnerable version range.
  3. Verify the vulnerable upgrade handler exists
    If SSH access is available, run 'ls -la /usr/bin/one_click_upgrade' to confirm the binary exists. This is the component containing the command injection flaw.
    Affected if The file /usr/bin/one_click_upgrade exists on the device, confirming the vulnerable component is present.
  4. Check if online firmware upgrade feature is accessible
    In the admin panel, verify the Online Firmware Upgrade option is present and not disabled. Look for the one-click upgrade functionality under System or Upgrade settings.
    Affected if The online firmware upgrade feature is enabled and accessible, providing the attack surface for command injection.

You are affected if you own a GL-MT3000 router running firmware version 4.4.5 or earlier with the /usr/bin/one_click_upgrade binary present and the online upgrade feature accessible.

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 GL-MT3000 firmware to version 4.7 or later to remediate this command injection vulnerability.

Recommended fix High confidence

4.7

  1. Identify the current firmware version of the GL-MT3000 router
  2. Download firmware version 4.7 for GL-MT3000 from the official GL.iNet website (fw.gl-inet.com)
  3. Access the router's web administration interface
  4. Navigate to the firmware upgrade section
  5. Upload the version 4.7 firmware file
  6. Wait for the upgrade process to complete and the router to reboot
  7. Verify the firmware has been updated to version 4.7

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-12187 — 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-12187 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