/

CVE-2026-92397

Severity:

CRITICAL RISK

(9.1)

OS Command Injection (CWE-78) in Ruijie RG-EW3000GX

CVE-2026-92397

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-77, CWE-78

Impact:

Remote Code Execution and Network Device Compromise

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 vulnerability in the Ruijie RG-EW3000GX router affects the cc_set function in the unifyframe-sgi.elf component. A remote attacker may be able to manipulate the data.url argument and cause operating-system commands to run when the affected configuration-change functionality processes the input.

Affected context

The vulnerability occurs in Ruijie RG-EW3000GX devices running the affected EW_3.0(1)B11P380 firmware. It is associated with the configChange component and its cc_set function, where remotely supplied input may reach command-processing logic through the data.url argument. Exposure depends on whether the relevant management functionality is reachable by an attacker and accepts insufficiently constrained input.

Exploit preconditions

  • Attack surface: Network-accessible router management or configuration-change functionality
  • Required access: Network reachability to the affected interface; additional authentication requirements may depend on deployment configuration
  • Trigger point: Processing of the data.url argument by the cc_set function in unifyframe-sgi.elf
  • Why exploitation is possible: Input may be incorporated into an operating-system command without adequate separation between data and command syntax

Why this happens

The underlying bug is an operating-system command-injection flaw. The affected configuration handler appears to process attacker-influenced URL data in a way that can allow input to alter command execution rather than remain ordinary data. This maps primarily to CWE-78: Improper Neutralization of Special Elements used in an OS Command, with CWE-77: Improper Neutralization of Special Elements used in a Command describing the broader command-injection class.

Potential impact

  • An attacker may execute arbitrary commands with the privileges of the affected service
  • The router could be taken over or rendered unavailable
  • Configuration settings, credentials, or network traffic could be exposed
  • The device could be used to access other systems on the local network
  • Persistent compromise or malicious traffic redirection could occur

General mitigation guidance

Mitigation generally focuses on ensuring that externally supplied values cannot become command syntax.

Common defensive patterns include:

  • Prefer direct library or API calls over shell command construction
  • Apply strict allowlist validation for URL fields, including scheme, host, path, and character constraints
  • Keep user-controlled data separated from command arguments through safe process-invocation interfaces
  • Avoid shell interpretation and remove unnecessary command execution from configuration handlers
  • Run management services with the minimum permissions required for their function
  • Restrict management interfaces to trusted administrative networks and apply strong access controls
  • Use network segmentation and read-only or integrity-protected configuration where practical

How teams detect issues like this

Organizations can look for this issue through:

  • Static-analysis rules identifying string concatenation or formatting of request data into shell commands
  • Code-review checks for command execution in configuration and URL-processing handlers
  • Firmware and binary analysis focused on command-spawning functions reachable from network-facing services
  • Runtime monitoring for unexpected child processes, shell invocations, or configuration changes on routers
  • Network detection for anomalous management requests and outbound connections originating from the device
  • Policy enforcement requiring allowlist validation and approved process-execution APIs for security-sensitive code

Automated code-review and software-composition tools may help identify related command-injection patterns, but findings should be validated against the device's actual execution paths.

Sources

SourceLink
github.comgithub.com/FoundTL/RG-EW3000GX/blob/main/RG-EW3000GX_unifyframe-sgi.elf.md
vuldb.comvuldb.com/cve/CVE-2026-92397
vuldb.comvuldb.com/submit/940161
vuldb.comvuldb.com/vuln/405549
vuldb.comvuldb.com/vuln/405549/cti

Frequently asked

questions

Yes, the description identifies a remote attack path. Practical exploitability depends on reachability of the affected configuration-change interface and any authentication or access controls protecting it.

Not necessarily. The key requirement is access to the vulnerable functionality; whether authentication is required depends on the router's exposure and administrative configuration.

Remove shell-based command construction where possible. Otherwise, use safe process APIs, strictly validate URL components with allowlists, and ensure user-controlled values are never interpreted as command syntax.

Combine secure input handling, least-privilege service accounts, restricted management-plane exposure, code review for command execution, and monitoring for unexpected processes or configuration changes.

Find out what's already
exploitable in your codebase.