CVE-2026-2534VulnerabilityPublished 16 Feb 2026Updated 23 Feb 2026

CVE-2026-2534: Comfast CF-N1 V2 · Command Injection

Affects Comfast CF-N1 V2Source CVE Database V5

Not known to be exploited · 15% EPSS · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Feb 2026
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-26.

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
ComfastCF-N1 V2	Affected =2.6.0.2	Fixed in–

AI-suggested

These include isolating the affected devices from untrusted networks and restricting access to the device management interfaces via network segmentation and firewall rules. Monitoring network traffic for unusual requests to the /cgi-bin/mbox-config endpoint and specifically for suspicious bandwidth parameter values can help detect exploitation attempts. Disabling or restricting remote management features on the device, if possible, reduces exposure. Organizations should consider replacing or upgrading affected devices to models with vendor-supported firmware that addresses this vulnerability. Additionally, applying strict input validation and web application firewall (WAF) rules to block command injection patterns targeting this endpoint can provide temporary protection. Regularly auditing device configurations and firmware versions across the network is critical to identify and remediate vulnerable instances promptly.

Description

A vulnerability has been found in Comfast CF-N1 V2 2.6.0.2. The affected element is the function sub_44AC4C of the file /cgi-bin/mbox-config?method=SET&section=ptest_bandwidth. The manipulation of the argument bandwidth leads to command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2026-2534 is the potential for remote attackers to execute arbitrary commands on Comfast CF-N1 V2 devices, compromising device integrity and availability. This could lead to unauthorized control over network infrastructure, enabling attackers to disrupt wireless connectivity, intercept or manipulate network traffic, or use the device as a foothold for further attacks within an organization’s network. Given the device’s role in wireless networking, exploitation could affect business continuity, data confidentiality, and operational stability. The lack of vendor response and patches increases the risk of exploitation, especially in environments where these devices are widely deployed. Organizations relying on these devices may face increased exposure to targeted attacks, including espionage, sabotage, or ransomware campaigns leveraging compromised network equipment.

Summary

CVE-2026-2534 identifies a command injection vulnerability in the Comfast CF-N1 V2 wireless device firmware version 2.6.0.2. The vulnerability resides in the function sub_44AC4C within the /cgi-bin/mbox-config CGI endpoint, which processes the 'bandwidth' parameter. Improper input validation allows an attacker to inject arbitrary OS commands by manipulating this parameter, leading to remote code execution. The attack vector is network-based, requiring no authentication or user interaction, making exploitation relatively straightforward for a remote attacker. The vendor was notified early but has not issued any patches or advisories. The vulnerability has been publicly disclosed, increasing the risk of exploitation. The CVSS 4.0 vector indicates low complexity (AC:L), no privileges required (PR:L but no authentication needed), and partial impact on confidentiality, integrity, and availability. Although no known exploits in the wild have been reported yet, the availability of public exploit information heightens the threat. This vulnerability could be leveraged to take control of affected devices, disrupt network operations, or pivot to internal networks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:17 UTC

Technical details

References

Community reviews

Related threats