TOZED X300 Firmware Faces Unpatched Critical Remote Code Execution Flaw CVE-2026-108576
A critical OS command injection vulnerability in TOZED X300 firmware allows remote attackers to execute arbitrary commands without authentication.
Key points
- CVE-2026-108576 carries a CVSS score of 10.0, rated Critical by the National Vulnerability Database.
- The flaw exists in the IPPingDiagnostics Handler component of TOZED X300 firmware versions up to 6.01.3.
- The vendor was contacted regarding the disclosure but has not provided a response or a fix.
Researchers have identified a critical remote code execution vulnerability in TOZED X300 firmware that allows attackers to inject operating system commands. The flaw, tracked as CVE-2026-108576, affects the IPPingDiagnostics Handler component and enables unauthenticated remote exploitation.
At a glance
- CVE
- CVE-2026-108576
- Product
- TOZED X300
- CVSS
- 10 Critical
- Weakness
- OS command injection
- Exploited
- No known exploitation
The National Vulnerability Database rates the severity of CVE-2026-108576 as Critical with a CVSS score of 10.0. The vulnerability stems from improper input validation in the process_ping function. Attackers can manipulate the Host argument to achieve OS command injection, granting them full control over the affected device.
Technical Details and Vendor Response
The weakness is classified under CWE-78 and CWE-77, indicating failures in neutralizing special elements in OS commands. The IPPingDiagnostics Handler fails to sanitize user-supplied input before passing it to system commands. This design flaw allows remote attackers to execute arbitrary code on the network device.
Disclosers contacted the vendor early in the disclosure process to report the security issue. According to the NVD record, the vendor did not respond in any way to these communications. No patch, update, or mitigation guidance has been confirmed by the manufacturer as of this report.
Affected Systems and Versions
What to do and how to stay safe
- Patch scores alone ignore context like network exposure and asset criticality.
- You must map vulnerabilities to specific business risks to prioritize correctly.
- Continuous exposure data replaces static scanning for accurate prioritization.
Prioritize vulnerabilities by actual exploitability and business impact, not by theoretical severity scores. Update your asset context and exposure data continuously to maintain accurate risk rankings.
Step-by-step guide: Risk Based Vulnerability Management: Prioritize Fixes by Actual Threat
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
