# CVE-2025-32458: ON Semiconductor Quantenna router_command.sh (in the get_syslog_from_qtn argument) Argument Injection

> Local attackers can execute arbitrary commands via argument injection in the router_command.sh script of Quantenna Wi-Fi chipsets.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2025
- **Updated:** 10 Jun 2025
- **Also known as:** GHSA-cgwq-jph9-cvc2

## What is CVE-2025-32458?

CVE-2025-32458 is a high-severity command injection vulnerability in ON Semiconductor Quantenna Wi-Fi chipset, published on 8 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Quantenna Wi-Fi chipset ships with a local control script, router_command.sh (in the get_syslog_from_qtn argument), that is vulnerable to command injection. This is an instance of CWE-88, "Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')," and is estimated as a CVSS 7.7 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).
This issue affects Quantenna Wi-Fi chipset through version 8.0.0.28 of the latest SDK, and appears to be unpatched at the time of this CVE record's first publishing, though the vendor has released a best practices guide for implementors of this chipset.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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

It affects 18 products.


Products: Onsemi Qcs-Ax2-A12 Firmware, Onsemi Qcs-Ax2-S5 Firmware, Onsemi Qcs-Ax2-T12 Firmware, Onsemi Qcs-Ax2-T8 Firmware, Onsemi Qcs-Ax3-A12 Firmware, Onsemi Qcs-Ax3-S5 Firmware, Onsemi Qcs-Ax3-T12 Firmware, Onsemi Qcs-Ax3-T8 Firmware, Onsemi Qd840 Firmware, Onsemi Qhs710 Firmware, Onsemi Qsr10ga Firmware, Onsemi Qsr10gu Firmware, Onsemi Qv840 Firmware, Onsemi Qv840c Firmware, Onsemi Qv860 Firmware, Onsemi Qv940 Firmware, Onsemi Qv942c Firmware, Onsemi Qv952c Firmware.

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

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

## Is CVE-2025-32458 being exploited?

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

## Other vulnerabilities in ON Semiconductor Quantenna Wi-Fi chipset

- [CVE-2025-3461](https://insights.sbomify.com/CVE-2025-3461/): ON Semiconductor Quantenna Telnet Missing Authentication (critical 9.1)
- [CVE-2025-32455](https://insights.sbomify.com/CVE-2025-32455/): ON Semiconductor Quantenna router_command.sh (in the run_cmd argument) Argument Injection (high 7.7)
- [CVE-2025-32456](https://insights.sbomify.com/CVE-2025-32456/): ON Semiconductor Quantenna router_command.sh (in the put_file_to_qtn argument) Argument Injection (high 7.7)
- [CVE-2025-32457](https://insights.sbomify.com/CVE-2025-32457/): ON Semiconductor Quantenna router_command.sh (in the get_file_from_qtn argument) Argument Injection (high 7.7)
- [CVE-2025-32459](https://insights.sbomify.com/CVE-2025-32459/): ON Semiconductor Quantenna router_command.sh (in the sync_time argument) Argument Injection (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32458 is a high-severity command injection vulnerability in ON Semiconductor Quantenna Wi-Fi chipset, published on 8 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32458 in the wild and no public exploit code.

Affected product: ON Semiconductor Quantenna Wi-Fi chipset. 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-32458/ (Markdown: https://insights.sbomify.com/CVE-2025-32458/index.md)
```

## Sources

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

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