Is CVE-2026-16097 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-16097 being exploited in the wild.

How severe is CVE-2026-16097?

High severity, with a CVSS score of 8.8, published 18 July 2026.

Which products and versions are affected?

MariuszNM Tomato PL ND 1.28 beta; Shibby Tomato 1.28.

Is there a fix for CVE-2026-16097?

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-16097 attacked?

It is attacked over the network, in device firmware.

Am I affected by CVE-2026-16097?

Check whether you run MariuszNM Tomato PL ND or 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.

CVE-2026-16097: Shibby Tomato stack overflow and command injection in Scheduler Name Handler

CVE-2026-16097 · Severity: high · CVSS 8.8 · Published 2026-07-18

A vulnerability exists in the Shibby Tomato and Tomato PL firmware, which are used to manage various home and small office routers. The flaw is located in the system's task scheduler, which handles automated background operations. An attacker could exploit this to crash the router or potentially take full control of the device, leading to data interception or network disruption.

Technologies: Shibby Tomato. Vendors: Shibby.

Quick answers

Is CVE-2026-16097 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-16097 being exploited in the wild.
How severe is CVE-2026-16097?: High severity, with a CVSS score of 8.8, published 18 July 2026.
Which products and versions are affected?: MariuszNM Tomato PL ND 1.28 beta; Shibby Tomato 1.28.
Is there a fix for CVE-2026-16097?: 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-16097 attacked?: It is attacked over the network, in device firmware.
Am I affected by CVE-2026-16097?: Check whether you run MariuszNM Tomato PL ND or 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

A stack-based buffer overflow and OS command injection vulnerability exists in the 'sbin/rc' component of Tomato firmware, specifically within the 'sub_42537C' function called by 'sched_main'. The vulnerability is caused by the unsafe use of 'sprintf' to format a 64-byte stack buffer with an attacker-controlled scheduler name argument ('a1'). Because the scheduler name is inserted into the command string multiple times without length validation or shell escaping, an attacker can overflow the buffer to overwrite the saved return address or inject shell metacharacters into a subsequent 'system()' call. While default initialization uses safe, fixed names, the vulnerability is reachable if an attacker can influence the scheduler name via authenticated web or API interfaces. This project is superseded by FreshTomato.

Affected products

Shibby Tomato 1.28
MariuszNM Tomato PL ND 1.28 beta

Timeline

2026-06-10: disclosed: Initial report by Fengyi Wang via Gitee
2026-07-18: advisory: NVD/VulDB publication

References

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