/

CVE-2026-75094

Severity:

CRITICAL RISK

(9.1)

OS Command Injection (CWE-78) in COMFAST CGI Interface

CVE-2026-75094

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-77, CWE-78

Impact:

Remote Code Execution

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical command-injection flaw in the COMFAST CF-N1-S CGI interface allows remotely supplied ssid input to reach operating-system command processing without adequate separation or validation. An attacker who can reach the affected endpoint may execute unauthorized commands with the privileges of the web service.

Affected context

The vulnerability occurs in the CGI interface endpoint associated with ptest_ssid configuration and the ssid argument. It may affect deployments where the endpoint is network-reachable and request data is incorporated into operating-system command execution without a sufficiently strict trust boundary.

Exploit preconditions

  • Attack surface: Network-accessible CGI interface
  • Required access: Ability to send requests to the affected endpoint; authentication requirements may depend on device configuration
  • Trigger point: Processing of the ssid argument by the ptest_ssid configuration function
  • Why exploitation is possible: User-controlled input is passed into an operating-system command context without reliable command/data separation

Why this happens

The underlying bug is an OS command-injection pattern in which externally controlled input is incorporated into a shell or command execution pathway. This maps primarily to CWE-78: Improper Neutralization of Special Elements used in an OS Command, with CWE-77: Improper Neutralization of Special Elements in Output Used by a Downstream Component describing the broader command-construction weakness. The insecure pattern occurs when application data is treated as part of command syntax rather than as a constrained argument.

Potential impact

  • An attacker may execute arbitrary commands on the affected device
  • The device could be altered, disrupted, or rendered unavailable
  • Sensitive configuration or network data could be exposed
  • The device may be used as a foothold for further network activity
  • Connected services or systems could be affected depending on device privileges and segmentation

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from application workflows and reducing trust in request parameters.

Common defensive patterns include:

  • Prefer direct process APIs that pass arguments separately rather than invoking a shell
  • Use strict allowlists for values such as network names and configuration identifiers
  • Apply context-appropriate validation before any system interaction
  • Avoid constructing commands through string concatenation or formatting
  • Run CGI services with the minimum required operating-system privileges
  • Restrict management interfaces through authentication, network segmentation, and least-privilege policy
  • Use secure-by-default administrative exposure and disable unnecessary remote management paths

How teams detect issues like this

Detection can combine code analysis, runtime monitoring, and administrative policy controls.

  • Use static-analysis rules to identify request parameters flowing into shell execution, command builders, or process-launch APIs
  • Review CGI handlers for string concatenation involving query parameters and system commands
  • Flag missing allowlists or validation for configuration fields that reach operating-system interfaces
  • Monitor web-service processes for unexpected child processes, command interpreters, or unusual outbound connections
  • Enforce policies that prohibit shell-based command execution for network-controlled input
  • Automated security review tools may help identify data flows from HTTP parameters into command execution sinks

Sources

SourceLink
github.comgithub.com/1ChaoRen1/IOT_1
vuldb.comvuldb.com/cve/CVE-2026-75094
vuldb.comvuldb.com/submit/877482
vuldb.comvuldb.com/vuln/391346
vuldb.comvuldb.com/vuln/391346/cti

Frequently asked

questions

Yes. The vulnerability is described as remotely exploitable when an attacker can reach the affected CGI endpoint. The practical scope depends on network exposure, authentication, and device access controls.

Not necessarily. The required access depends on how the device protects its CGI interface and whether the endpoint is exposed to an untrusted network.

The safest pattern is to eliminate shell interpretation, pass fixed arguments through a direct process API, and enforce strict allowlist validation for accepted ssid values.

Treat all request parameters as untrusted, prohibit command construction from raw input, apply least privilege to management services, and combine code review with automated data-flow analysis.

Find out what's already
exploitable in your codebase.