CVE-2025-3460VulnerabilityPublished 8 Jun 2025

CVE-2025-3460: ON Semiconductor Quantenna Wi-Fi chipset · Argument Injection

Affects ON Semiconductor Quantenna Wi-Fi chipsetSource CVE Database V5

Not known to be exploited · CVSS 7.7 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ON Semiconductor Quantenna Wi-Fi chipset	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-3460, European organizations should take several specific steps beyond generic patching advice: 1) Conduct an immediate inventory of all networking devices to identify those using the Quantenna Wi-Fi chipset and verify the SDK version. 2) Apply network segmentation to isolate Wi-Fi infrastructure devices from general user networks, limiting local access to trusted administrators only. 3) Implement strict access controls and monitoring on devices with local management interfaces to detect and prevent unauthorized access attempts. 4) Follow the vendor's best practices guide for secure implementation of the chipset, which may include disabling or restricting the set_tx_pow script or replacing it with a hardened alternative. 5) Employ host-based intrusion detection systems (HIDS) on critical devices to detect suspicious command execution or script usage. 6) Where possible, restrict physical access to networking hardware to prevent local exploitation. 7) Engage with vendors and monitor for patch releases, planning rapid deployment once available. 8) Educate network administrators about the risks of local command injection vulnerabilities and the importance of secure configuration and monitoring.

Description

The Quantenna Wi-Fi chipset ships with a local control script, set_tx_pow, 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.

Impact

For European organizations, the impact of CVE-2025-3460 could be substantial, especially for those relying on networking equipment incorporating the Quantenna Wi-Fi chipset. Compromise of Wi-Fi infrastructure can lead to exposure of sensitive communications, unauthorized network access, and potential lateral movement within corporate networks. This is particularly critical for sectors with stringent data protection requirements such as finance, healthcare, and government agencies. The vulnerability's requirement for local access means that attackers would need to have physical or network-level access to the device, which could be achieved through compromised internal networks or malicious insiders. Given the widespread deployment of Wi-Fi devices in offices, manufacturing plants, and public spaces, exploitation could disrupt business operations and lead to data breaches. Moreover, the lack of an available patch increases the window of exposure. European organizations must consider the risk of this vulnerability in their asset inventories and network segmentation strategies to prevent attackers from reaching vulnerable devices.

Summary

CVE-2025-3460 is a high-severity vulnerability (CVSS 7.7) affecting the ON Semiconductor Quantenna Wi-Fi chipset, specifically through version 8.0.0.28 of its SDK. The vulnerability arises from improper neutralization of argument delimiters in a local control script named set_tx_pow, which is used to set the transmission power of the Wi-Fi chipset. This flaw is categorized under CWE-88, indicating an 'Argument Injection' vulnerability where unsanitized input can be injected into command arguments. Because the set_tx_pow script runs locally and does not require user interaction or privileges (PR:N, UI:N), an attacker with local access to the device could exploit this vulnerability to execute arbitrary commands with the privileges of the script. The impact of this vulnerability is significant, as it allows for full compromise of confidentiality and integrity of the affected device's system, though it does not affect availability. Exploitation requires local access to the device, which limits the attack vector primarily to insiders or attackers who have already breached perimeter defenses. No known exploits in the wild have been reported yet. The vulnerability affects a widely used Wi-Fi chipset embedded in various networking devices, potentially impacting many IoT and enterprise-grade wireless access points and routers that use this chipset. Given the critical role of Wi-Fi infrastructure in modern networks, exploitation could lead to unauthorized data access, manipulation of network traffic, or pivoting to other internal systems.

CWE-88Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') (opens in a new tab)
Base weaknessOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.
Implementation · Parameterization
Where possible, avoid building a single string that contains the command and its arguments. Some languages or frameworks have functions that support specifying independent arguments, e.g. as an array, which is used to automatically perform the appropriate quoting or escaping while building the command.
Architecture and Design · Input Validation
Understand all the potential areas where untrusted inputs can enter your product: parameters or arguments, cookies, anything read from the network, environment variables, request headers as well as content, URL components, e-mail, files, databases, and any external systems that provide data to the application.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
Flash Parameter Injection (opens in a new tab)
Using Meta-characters in E-mail Headers to Inject Malicious Payloads (opens in a new tab)
HTTP Parameter Pollution (HPP) (opens in a new tab)
OS Command Injection (opens in a new tab)
Parameter Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2025, 01:26 UTC

WeaknessesCWE-88

Technical details

References

Community reviews

Related threats