CVE-2026-10873: Shibby Tomato OS command injection in rstats_path

CVE-2026-10873 · Severity: high · CVSS 7.2 · Published 2026-06-04

A vulnerability exists in the Shibby Tomato router firmware, specifically within its bandwidth monitoring component. An attacker with administrative access can provide a specially crafted file path that allows them to execute unauthorized commands on the router's operating system. This could lead to a complete takeover of the device, potentially compromising the entire network it manages.

Technologies: Shibby Tomato. Vendors: Shibby.

Quick answers

Is CVE-2026-10873 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-10873 being exploited in the wild.
How severe is CVE-2026-10873?
High severity, with a CVSS score of 7.2, published 4 June 2026.
Which products and versions are affected?
Shibby Tomato 1.28.0000.
Is there a fix for CVE-2026-10873?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-10873 attacked?
It is attacked over the network, in device firmware.
Am I affected by CVE-2026-10873?
Check whether you run Shibby Tomato at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An OS command injection vulnerability exists in the /bin/rstats binary of Shibby Tomato firmware version 1.28.0000. The rstats_path function retrieves the 'rstats_path' value from NVRAM and passes it to a system() call via sprintf without adequate shell metacharacter filtering. An attacker with Web UI administrative credentials can exploit this by navigating to Admin -> Bandwidth Monitoring and setting a custom 'f_user' path containing shell injectors (e.g., using semicolons or hash marks). The vulnerability is triggered when the rstats service restarts or processes the path. While Shibby Tomato is superseded by FreshTomato, which has hardened this component using zlib and snprintf, the original Shibby branch remains vulnerable.

Affected products

  • Shibby Tomato 1.28.0000 MIPSR2-124 K26 USB Big-VPN 1.28.0000

Timeline

  • 2026-05-17: disclosed: Initial disclosure by researcher WH-YHUST
  • 2026-06-04: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.