Quick answers
- Is CVE-2026-10066 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10066 being exploited in the wild.
- How severe is CVE-2026-10066?
- High severity, with a CVSS score of 8.8, published 29 May 2026.
- Which products and versions are affected?
- Shibby Tomato by Shibby up to 1.28.
- Is there a fix for CVE-2026-10066?
- 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-10066 attacked?
- It is attacked over the network, in device firmware.
- Am I affected by CVE-2026-10066?
- Check whether you run Shibby Tomato by Shibby 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 exists in the 'tomatoups.cgi' component of Shibby Tomato firmware (up to version 1.28). The vulnerability is located in function 'sub_9068', which parses text protocol fields from a UPS service over TCP port 3551. The root cause is a failure to enforce length limits when using 'sscanf' with the '%s' format specifier and during byte-by-byte copy operations. Specifically, when handling the 'upstemp' field, an attacker-controlled UPS response exceeding 64 bytes can overwrite the stack, leading to memory corruption and potential remote code execution. This has been verified via dynamic analysis in QEMU. As the project is superseded by FreshTomato and no longer supported, no official patch is expected.
Affected products
- Shibby Tomato by Shibby up to 1.28
Timeline
- 2026-05-02: disclosed: Initial vulnerability report by Fengyi Wang
- 2026-05-29: advisory: CVE-2026-10066 published by VulDB/NVD