# CVE-2026-86530: Command injection in WEX-G300

> An administrative user can execute arbitrary OS commands on BUFFALO Wi-Fi routers via crafted HTTP requests due to improper input handling.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-j628-7w6r-937x

## What is CVE-2026-86530?

CVE-2026-86530 is a high-severity command injection vulnerability in BUFFALO INC. WEX-G300, published on 28 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

BUFFALO Wi-Fi products handle some web form input improperly to assemble command line strings internally. An administrative user may send a crafted HTTP request and execute an arbitrary OS command.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-86530 being exploited?

There is no known exploitation of CVE-2026-86530 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86530 is a high-severity command injection vulnerability in BUFFALO INC. WEX-G300, published on 28 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86530 in the wild and no public exploit code.

Affected product: BUFFALO INC. WEX-G300. 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-86530/ (Markdown: https://insights.sbomify.com/CVE-2026-86530/index.md)
```

## Sources

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

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