dbcve.org
InjectionWeakness · CWE-74

CVE-2026-12186

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 weakness has been identified in GL.iNet GL-MT3000 up to 4.4.5. Affected is the function replace_country in the library /usr/lib/oui-httpd/rpc/tor of the component Tor Proxy Service Configuration Handler. This manipulation causes command injection. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 4.7 is able to address this issue. It is recommended to upgrade the affected component. 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

A command injection vulnerability exists in the replace_country function within the Tor Proxy Service Configuration Handler (library /usr/lib/oui-httpd/rpc/tor) of GL.iNet GL-MT3000 routers up to version 4.4.5. The vulnerability allows remote attackers to execute arbitrary commands due to insufficient input sanitization in the affected function.

MitigationUpgrade the 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. Identify the router model
    Check /etc/config/glconfig or run 'uci get system.@system[0].model' or inspect the device label to confirm it is a GL-MT3000
    Affected if The device is not a GL-MT3000 - this specific vulnerability only affects that model
  2. Check the installed firmware version
    Run 'cat /etc/glib_version' or 'uci get system.@system[0].version' to retrieve the current firmware version
    Affected if Firmware version is 4.4.5 or lower - versions up to 4.4.5 are vulnerable; version 4.7 and later are fixed
  3. Verify the Tor proxy service is present
    Check if /usr/lib/oui-httpd/rpc/tor exists on the device using 'ls -la /usr/lib/oui-httpd/rpc/tor'
    Affected if The vulnerable file /usr/lib/oui-httpd/rpc/tor is present - the command injection exists in the replace_country function within this file
  4. Check if Tor proxy is configured or enabled
    Inspect /etc/config/tor or run 'uci show tor' to see if any Tor proxy configuration exists
    Affected if Tor proxy is actively configured - the exploit targets the replace_country function in the Tor proxy configuration handler

A GL-MT3000 router with firmware version 4.4.5 or lower that has the Tor proxy service configured is affected by this command injection vulnerability in the replace_country function.

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

Recommended fix High confidence

version 4.7

  1. Access the GL-MT3000 router's web admin interface by navigating to the device's IP address (typically 192.168.1.1)
  2. Log in with administrator credentials
  3. Navigate to the 'System' or 'Firmware' settings section
  4. Locate the firmware upgrade option
  5. Download the official firmware version 4.7 from fw.gl-inet.com or the official GL.iNet support portal
  6. Upload the firmware file to the router through the web interface
  7. Wait for the upload to complete and allow the router to reboot automatically
  8. After reboot, verify the firmware version has been updated to 4.7 in the system information section
Caveat Standard firmware upgrade risk - ensure stable power during upgrade to avoid device brickage; backup configuration if possible

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12186 — 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-12186 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