/

CVE-2026-92398

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-92398

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 command injection vulnerability in the Ruijie RG-EW3000GX may allow a remote attacker to cause operating-system commands to run through the user_list_note functionality.

The issue becomes risky when externally influenced Name data reaches the affected administrative configuration handling without strict validation and safe command construction.

Affected context

The vulnerability occurs in Ruijie RG-EW3000GX devices running the affected EW_3.0(1)B11P380 firmware, within functionality associated with the user_list_note module and the /etc/rg_config/admin configuration area. Exposure depends on whether the relevant management interface is reachable by an attacker and whether supplied Name values are processed by the affected command-handling path.

Exploit preconditions

  • Attack surface: A remotely reachable device management or application interface
  • Required access: Access sufficient to submit or influence the relevant user-list note data; authentication requirements depend on deployment configuration
  • Trigger point: Processing of the Name argument by the affected user_list_note functionality
  • Why exploitation is possible: Insufficient separation between user-controlled data and operating-system command syntax may allow supplied input to alter the intended command execution context

Why this happens

The underlying flaw is an OS command injection condition mapped primarily to CWE-78: Improper Neutralization of Special Elements used in an OS Command. The affected code appears to incorporate externally influenced input into an operating-system command or command-like operation without adequately constraining its meaning as data. CWE-77 is also relevant as a broader command-injection classification. This insecure pattern can cause input intended as a name or note to be interpreted as executable command content.

Potential impact

  • An attacker may execute commands with the privileges of the affected device service
  • Device configuration or network settings could be modified
  • Sensitive device or network information could be exposed
  • The device could be disrupted, persistently compromised, or used to attack adjacent systems
  • Administrative credentials or other stored data could be affected

General mitigation guidance

Mitigation generally focuses on ensuring that user-controlled values never become executable command syntax.

Common defensive patterns include:

  • Replacing shell-based operations with parameterized APIs or direct library calls
  • Applying strict allowlist validation appropriate for names and notes
  • Separating data values from command arguments and avoiding shell interpretation
  • Restricting management interfaces to trusted networks and authorized administrators
  • Running device services with the lowest practical privileges
  • Limiting outbound connectivity and isolating management-plane components
  • Preserving centralized logging and using secure-by-default administrative access controls

How teams detect issues like this

Organizations can look for this weakness through:

  • Static analysis rules identifying shell execution APIs that receive request, form, query, or configuration values
  • Code review checks for string concatenation or interpolation used to build operating-system commands
  • Tests that verify strict allowlist validation for fields expected to contain names or notes
  • Monitoring for unusual administrative requests, command-like characters in user-list fields, and unexpected device configuration changes
  • Network detection for anomalous management access or device-initiated connections
  • Security policy enforcement that restricts shell invocation and requires parameterized process APIs

Automated code review and software composition analysis tools may help identify related command-construction patterns.

Sources

SourceLink
github.comgithub.com/FoundTL/RG-EW3000GX/blob/main/RG-EW3000GX_user_list_note.md
vuldb.comvuldb.com/cve/CVE-2026-92398
vuldb.comvuldb.com/submit/940182
vuldb.comvuldb.com/vuln/405550
vuldb.comvuldb.com/vuln/405550/cti

Frequently asked

questions

Yes, the reported issue can be initiated remotely when the affected management or application path is reachable and the attacker can submit data processed by the vulnerable functionality.

The available description does not establish a universal authentication requirement. The practical prerequisite is access to the relevant interface and permission to influence the Name argument, which depends on device configuration and deployment controls.

The safest pattern is to eliminate shell interpretation, use direct parameterized APIs, and enforce strict allowlist validation for values that represent names or notes.

Treat all interface-provided values as untrusted, prohibit command construction through string concatenation, apply least privilege, restrict management exposure, and include command-injection testing in code review and security validation.

Find out what's already
exploitable in your codebase.