CVE-2026-12197: Ruijie EG105G-P Command Injection Vulnerability (CVSS 7.2)
A command injection vulnerability exists in Ruijie EG105G-P version 2.340, specifically in the network diagnostic endpoint accessible via the web interface. An authenticated attacker can manipulate the target parameter of the nslookup function to inject and execute arbitrary system commands on the affected device. The vulnerability is remotely exploitable and public exploit code has been released. The vendor has not responded to early disclosure efforts.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.2 HIGH · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-74, CWE-77
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-15 / 2026-06-17
NVD description (verbatim)
A security flaw has been discovered in Ruijie EG105G-P 2.340. The impacted element is the function nslookup of the file /cgi-bin/luci/api/diagnose of the component JSON-RPC Diagnose Endpoint. Performing a manipulation of the argument params.target results in command injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
5 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-12197 affects the JSON-RPC Diagnose Endpoint in Ruijie EG105G-P 2.340. The vulnerable code path is /cgi-bin/luci/api/diagnose, specifically the nslookup function. Insufficient input validation on the params.target argument allows an authenticated user to break out of the intended command context and inject shell metacharacters, leading to arbitrary command execution with the privileges of the web service process. The vulnerability is classified as CWE-74 (Improper Neutralization of Special Elements in Output) and CWE-77 (Improper Neutralization of Special Elements used in a Command), indicating both encoding and command-level injection flaws.
Business impact
Successful exploitation allows an authenticated user to achieve remote code execution on Ruijie network appliances, potentially leading to complete device compromise. In enterprise deployments where EG105G-P units serve as gateways or diagnostic hubs, this could enable lateral movement, network segmentation bypass, data exfiltration, or denial of service. The availability of public exploit code significantly increases the likelihood of weaponized attacks. Organizations relying on these devices for network management or security appliance functions face direct operational risk.
Affected systems
Ruijie EG105G-P version 2.340 is confirmed affected. The vulnerable endpoint is present in the web administration interface. Organizations using this product should assume exposure unless running a patched version. Verify the exact firmware version on deployed units, as earlier or later versions may also be vulnerable—vendor confirmation is essential before ruling out any deployment.
Exploitability
Exploitation requires authentication to the web interface, which typically means valid administrative credentials or network access to the management VLAN. However, the public availability of exploit code and the relative simplicity of the injection technique lower the barrier for motivated attackers, especially in environments with weak credential hygiene or default credentials. The CVSS vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) reflects network-accessible attack with high privileges required but low attack complexity; the lack of user interaction and universal impact scope indicate severe consequences once the authentication hurdle is cleared.
Remediation
Immediate actions: (1) Verify firmware version on all Ruijie EG105G-P deployments. (2) Restrict administrative web interface access to trusted networks via firewall rules and access control lists. (3) Enforce strong, unique credentials on all management accounts and disable default accounts. (4) Monitor for suspicious diagnostic API calls in access logs. Long-term: Contact Ruijie support directly to obtain patched firmware. Given the vendor's non-responsiveness to early disclosure, monitor the CVE record and community channels for unofficial patches or vendor statements. Consider upgrading to alternative products if vendor support remains unavailable.
Patch guidance
As of the vulnerability publication date, the vendor has not released or announced patches despite early disclosure notification. Do not assume a patch is available; verify directly with Ruijie support for availability and release timelines. If a patch version is released, testing should occur in an isolated lab environment before production deployment, given the security-critical nature of this function. Document the patched firmware version and maintain a record of deployment completion.
Detection guidance
Monitor web server and application logs on affected devices for unusual patterns in /cgi-bin/luci/api/diagnose requests, particularly those containing shell metacharacters (pipe, semicolon, backticks, $(), &, |) in the params.target parameter. Network IDS/IPS signatures should alert on POST requests to this endpoint with suspicious payloads. Endpoint detection should flag command execution spawned from web server processes with unexpected parent-child relationships. Baseline normal diagnostic traffic to identify anomalies; legitimate nslookup operations should use standard domain names without special characters.
Why prioritize this
This vulnerability merits urgent remediation despite the authentication requirement. The combination of public exploit code, remote exploitability, high confidentiality/integrity/availability impact, and vendor non-responsiveness creates significant risk. Any organization with internet-facing or internally-exposed management interfaces must prioritize this immediately. Even in protected environments, the existence of public tooling means compromise is likely if an attacker gains any form of authenticated access—making this a critical chaining vulnerability in multi-stage attacks.
Risk score, explained
The CVSS 3.1 score of 7.2 (HIGH) reflects the severity of command execution with full system impact, but is moderated by the authentication requirement (PR:H). However, this scoring may underestimate real-world risk because: (1) many organizations reuse administrative credentials across devices, (2) the vendor is unresponsive, leaving no clear remediation path, and (3) public exploit code eliminates the need for exploit development. Organizations should treat this as a critical priority in their own risk assessment, particularly for network-critical appliances.
Frequently asked questions
Does this vulnerability affect Ruijie products other than EG105G-P?
CVE-2026-12197 is specifically reported against EG105G-P version 2.340. Related Ruijie products may be affected if they share the same vulnerable code path and version line, but that has not been confirmed. Check with Ruijie support for a full product compatibility matrix and scan your environment for any other Ruijie appliances running version 2.340 or related firmware branches.
What happens if we can't patch immediately?
Implement compensating controls: (1) restrict network access to the web management interface using firewall rules, allowing only known administrator IP addresses, (2) place the device behind a VPN or bastion host, (3) disable the diagnostic API if it is not actively used, (4) enforce multi-factor authentication if the appliance supports it, and (5) increase logging and monitoring for suspicious activity. These measures reduce but do not eliminate risk; patch deployment should remain the top priority once a vendor patch becomes available.
How can we tell if we've been compromised?
Check web server logs for requests to /cgi-bin/luci/api/diagnose with suspicious parameters, especially those containing shell metacharacters. Review system command execution logs and process audit trails for unexpected commands spawned by the web service user. Look for unusual outbound connections, file modifications, or privilege escalation attempts originating from the appliance. If public exploit code has been released and your device is accessible on the network, assume it is a likely target and conduct forensic analysis to determine if exploitation has occurred.
Should we replace the device or wait for a patch?
That depends on the device's role and your risk tolerance. If it is critical to network operations and the vendor provides no patch timeline, replacement may be warranted. If it is supplementary or can be fully isolated, waiting for a patch is reasonable. Contact Ruijie support immediately to establish a patch timeline. In the interim, implement the strongest compensating controls possible and evaluate alternative products from vendors with proven security response capabilities.
This analysis is based on publicly available vulnerability data as of the publication date. No guarantee is made regarding patch availability, vendor responsiveness, or the completeness of affected product lists. Readers should verify all patch version numbers and product compatibility against official vendor advisories and security notices. This document is for informational purposes only and does not constitute professional security advice; organizations should conduct their own risk assessments and consult with qualified security professionals. The details of public exploits are not provided; readers should handle any such code with appropriate caution and only in controlled, authorized environments. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-11450HIGHGL.iNet GL-MT3000 Remote Command Injection Vulnerability
- CVE-2026-11451HIGHGL.iNet GL-MT3000 Remote Command Injection in FTP Handler
- CVE-2026-11452HIGHGL.iNet GL-MT3000 Command Injection Vulnerability – Firmware Update Required
- CVE-2026-12186HIGHGL.iNet GL-MT3000 Command Injection in Tor Proxy Handler
- CVE-2026-12187HIGHGL.iNet GL-MT3000 Command Injection in Firmware Upgrade Handler
- CVE-2026-10060MEDIUMTRENDnet TEW-432BRP Command Injection—End-of-Life Router Vulnerability
- CVE-2026-10061MEDIUMTRENDnet TEW-432BRP Command Injection Vulnerability – Remediation via Replacement
- CVE-2026-10127MEDIUMEdimax BR-6478AC Command Injection in Firmware 1.23