/

CVE-2026-86299

Severity:

CRITICAL RISK

(9.9)

OS Command Injection (CWE-78) in Linksys RE7000 Handler

CVE-2026-86299

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-77, CWE-78

Impact:

Remote Code Execution

Severity:

CRITICAL RISK

(9.9)

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 OS command injection vulnerability in the Linksys RE7000 PingTest Handler allows attacker-controlled ping-test parameters to influence command execution. Because the affected endpoint can be reached remotely, an attacker may execute operating-system commands on the device when the vulnerable handler processes crafted input.

Affected context

The vulnerability occurs in the Linksys RE7000 2.0.15 web interface, specifically the platform_event_pingTest function exposed through /cgi-bin/json.cgi?PingTest. It may exist when remotely supplied values for pingTestIp, pingTestPktSize, or pingTestTimes are incorporated into operating-system command execution without sufficient separation, validation, or escaping.

Exploit preconditions

  • Attack surface: The remotely reachable PingTest Handler endpoint
  • Required access: Network access to the device's affected web interface; authentication requirements may depend on deployment configuration
  • Trigger point: Processing of the pingTestIp, pingTestPktSize, or pingTestTimes parameters
  • Why exploitation is possible: User-controlled parameter values may reach a shell or command-execution interface without adequate allowlisting and argument isolation

Why this happens

The underlying bug is command construction from untrusted request parameters. When application input is concatenated into a shell command or passed to an interpreter without strict validation and safe argument handling, control characters or command syntax may alter the intended operation. 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-injection class.

Potential impact

  • An attacker may execute arbitrary operating-system commands on the device
  • The device could be taken over or its configuration altered
  • Network traffic or connected systems may be exposed to further compromise
  • Attackers could disrupt connectivity or device availability
  • The device may be used to support lateral movement or other malicious activity

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from network-facing diagnostic functionality and reducing trust in request parameters.

Common defensive patterns include:

  • Invoking operating-system utilities through structured APIs with separate arguments rather than shell command strings
  • Applying strict allowlists and type, range, and length validation to diagnostic parameters
  • Rejecting unexpected characters and canonicalization ambiguities before processing input
  • Running network-facing services with the least privileges required for their function
  • Restricting administrative interfaces through network segmentation and secure access controls
  • Separating diagnostic operations from privileged system functions and applying resource limits

How teams detect issues like this

Organizations can look for:

  • Static-analysis findings involving shell execution, command construction, or string concatenation with HTTP parameters
  • Code-review signals such as request values passed to shell wrappers without structured argument handling
  • Runtime logs showing unusual PingTest requests, unexpected parameter characters, or abnormal command failures
  • Web-application and device policies that restrict administrative endpoints and monitor repeated diagnostic requests
  • Automated security review tools configured to identify CWE-77 and CWE-78 patterns

Sources

SourceLink
github.comgithub.com/limou89/somevul/blob/main/Linksys_RE7000_v2_PingTest_Command_Injection.md
vuldb.comvuldb.com/cve/CVE-2026-86299
vuldb.comvuldb.com/submit/906547
vuldb.comvuldb.com/vuln/399463
vuldb.comvuldb.com/vuln/399463/cti
linksys.comlinksys.com/

Frequently asked

questions

Yes. The affected PingTest endpoint is described as remotely reachable, although practical exploitability may still depend on network exposure and authentication controls.

An attacker needs network access to the affected handler. Whether authentication is required depends on how the device's management interface is exposed and configured.

Avoid shell-based command construction, use structured process APIs with fixed executable paths and separate arguments, and enforce strict validation for every diagnostic parameter.

Treat all request parameters as untrusted, apply allowlist validation, use least-privilege service accounts, isolate management interfaces, and include command-injection checks in code review and automated testing.

Find out what's already
exploitable in your codebase.