Is CVE-2026-10069 exploited in the wild?

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

How severe is CVE-2026-10069?

High severity, with a CVSS score of 7.5, published 29 May 2026.

Is there a fix for CVE-2026-10069?

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

It is attacked over the network, in device firmware.

Am I affected by CVE-2026-10069?

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.

CVE-2026-10069: Shibby Tomato resource exhaustion in miniupnpd

CVE-2026-10069 · Severity: high · CVSS 7.5 · Published 2026-05-29

A vulnerability exists in the Shibby Tomato firmware, which is software used to power various home and small office routers. An attacker can send specially crafted network requests to the router's UPnP service to consume all available system memory. This can cause the router to become slow, unresponsive, or crash, disrupting internet connectivity for all connected users.

Technologies: Shibby Tomato. Vendors: Shibby.

Quick answers

Is CVE-2026-10069 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-10069 being exploited in the wild.
How severe is CVE-2026-10069?: High severity, with a CVSS score of 7.5, published 29 May 2026.
Which products and versions are affected?: Shibby Tomato 1.28.
Is there a fix for CVE-2026-10069?: 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-10069 attacked?: It is attacked over the network, in device firmware.
Am I affected by CVE-2026-10069?: 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

A resource exhaustion vulnerability (CWE-400) exists in the 'miniupnpd' daemon (specifically version 1.8) within Shibby Tomato firmware 1.28. The vulnerability is located in the HTTP request buffering logic within 'usr/sbin/miniupnpd'. The daemon uses realloc() to extend a heap-backed buffer as it receives HTTP headers and POST bodies, but it fails to enforce a maximum request size limit. An unauthenticated attacker on the LAN can exploit this by sending incomplete HTTP headers or large 'Content-Length' headers followed by partial bodies, leading to continuous heap growth and eventual denial of service. While the project is superseded by FreshTomato, this legacy version remains vulnerable.

Affected products

Shibby Tomato by Shibby 1.28

Timeline

2026-04-22: disclosed: Vulnerability reported by Fengyi Wang via Gitee issue.
2026-05-29: advisory: CVE-2026-10069 published.

References

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