Quick answers
- Is CVE-2026-10065 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10065 being exploited in the wild.
- How severe is CVE-2026-10065?
- High severity, with a CVSS score of 8.8, published 29 May 2026.
- Which products and versions are affected?
- Shibby Tomato by Shibby 1.28.
- Is there a fix for CVE-2026-10065?
- 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-10065 attacked?
- It is attacked over the network, in device firmware.
- Am I affected by CVE-2026-10065?
- 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 (CWE-121) exists in the get_ups_field function within tomatodata.cgi of Shibby Tomato firmware version 1.28. The vulnerability is triggered when the CGI component processes UPS (Uninterruptible Power Supply) information. Specifically, the function performs an unbounded byte-copy of the 'DATE' field into a fixed-size 256-byte stack buffer without verifying the length against the provided buffer size. An attacker who can control the response from a UPS server (e.g., via a man-in-the-middle or a malicious UPS host) can provide a 'DATE' field exceeding 256 bytes to overwrite stack memory. This can lead to process crashes or remote code execution. The project is end-of-life and has been superseded by FreshTomato.
Affected products
- Shibby Tomato by Shibby 1.28
Timeline
- 2026-05-02: disclosed: Initial vulnerability report by Fengyi Wang
- 2026-05-29: advisory: CVE published via VulDB/NVD