# CVE-2025-67089: Command injection in n/a

> Authenticated attackers can execute arbitrary commands with root privileges via unsanitized input in the router's package installation RPC method.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2026
- **Updated:** 8 Jan 2026
- **Also known as:** GHSA-wxm8-fmqv-9x7q

## What is CVE-2025-67089?

CVE-2025-67089 is a high-severity command injection vulnerability in n/a, published on 8 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A command injection vulnerability exists in the GL-iNet GL-AXT1800 router firmware v4.6.8. The vulnerability is present in the `plugins.install_package` RPC method, which fails to properly sanitize user input in package names. Authenticated attackers can exploit this to execute arbitrary commands with root privileges

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-67089?

It affects 1 product.


Products: Gl-Inet Gl-Axt1800 Firmware.

## How do I fix CVE-2025-67089?

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

## Is CVE-2025-67089 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67089 and fix it if it is affected.

What it is: CVE-2025-67089 is a high-severity command injection vulnerability in n/a, published on 8 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67089 exists.

Affected product: n/a. 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-2025-67089/ (Markdown: https://insights.sbomify.com/CVE-2025-67089/index.md)
```

## Sources

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

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