Quick answers
- Is CVE-2026-10068 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10068 being exploited in the wild.
- How severe is CVE-2026-10068?
- High severity, with a CVSS score of 7.3, published 29 May 2026.
- Which products and versions are affected?
- Shibby Tomato by Shibby 1.28.
- Is there a fix for CVE-2026-10068?
- 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-10068 attacked?
- It is attacked over the network, in device firmware.
- Am I affected by CVE-2026-10068?
- 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
An out-of-bounds read vulnerability exists in the miniupnpd component (specifically the SUBSCRIBE Call Handler) of Shibby Tomato firmware version 1.28. The root cause is located in the 'send' function within usr/sbin/miniupnpd, where the daemon fails to validate the length of a formatted NOTIFY request against its fixed 1024-byte (0x400) heap buffer. By providing a specially crafted, long callback URI in a SUBSCRIBE request, an unauthenticated attacker on the LAN can cause snprintf() to return a value larger than the buffer size. Subsequent calls to send() use this unchecked length, resulting in the transmission of adjacent heap memory back to the attacker's listener. While initially categorized as SSRF (CWE-918), the primary impact is information disclosure (CWE-200) of sensitive heap data.
Affected products
- Shibby Tomato by Shibby 1.28
Timeline
- 2026-04-22: disclosed: Vulnerability reported by Fengyi Wang via Gitee.
- 2026-05-29: advisory: CVE-2026-10068 published.