# CVE-2026-11451: GL.iNet GL-MT3000 FTP Protocol glc snprintf command injection

> Remote attackers can execute arbitrary commands via the FTP protocol handler's media_dir argument in GL.iNet GL-MT3000 routers.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-rw8j-c4m6-h6r7

## What is CVE-2026-11451?

CVE-2026-11451 is a medium-severity command injection vulnerability in GL.iNet GL-MT3000, published on 7 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw has been found in GL.iNet GL-MT3000 4.4.5. This impacts the function snprintf of the file /cgi-bin/glc of the component FTP Protocol Handler. Executing a manipulation of the argument media_dir can lead to command injection. It is possible to launch the attack remotely. Upgrading to version 4.8.1 will fix this issue. You should upgrade the affected component. The vendor explains: "In version 4.8.1, before writing media_dir to the FTP configuration command, the code escapes single quotes using escape_single_quote(). The payloads in the report—which rely on closing a single quote, appending commands with a semicolon, and commenting out the tail with #—cannot escape execution under the current code path. We also verified this on a GL‑MT3000 device running firmware version 4.8.1 using similar payloads calling the /NAS_API_SET_PROTO_CONFIG interface. Although the interface returned success, the marker file intended to prove command execution was not created; the payload was written into /etc/vsftpd.conf only as ordinary configuration content and did not trigger any shell command execution. Therefore, with the current firmware version and default runtime environment, we could not reproduce the claimed “unauthorized command injection in set_proto_config”."

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-11451?


## How do I fix CVE-2026-11451?

No fix has been published for CVE-2026-11451 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11451 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11451 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11451 and fix it if it is affected.

What it is: CVE-2026-11451 is a medium-severity command injection vulnerability in GL.iNet GL-MT3000, published on 7 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11451 exists.

Affected product: GL.iNet GL-MT3000. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-11451/ (Markdown: https://insights.sbomify.com/CVE-2026-11451/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11451
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11451
- OSV: https://osv.dev/vulnerability/CVE-2026-11451

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-11451/
Summaries are generated and may contain mistakes; the official description above is the record.