A vulnerability has been found in Shibby Tomato 1.28. The impacted element is an unknown function of the file usr/sbin/miniupnpd. Such manipulation leads to resource consumption. The attack may be launched remotely. This project is superseded by FreshTomato. This vulnerability only affects products that are no longer supported by the maintainer.
Security readout for executives and security teams
Plain-English summary
This is a high-severity denial-of-service risk in legacy Shibby Tomato 1.28 router firmware. A remote attacker may be able to exhaust resources through the miniupnpd component, affecting device availability. The affected project is no longer supported, which increases remediation urgency for any remaining deployments.
Executive priority
Treat this as a near-term legacy infrastructure risk. The main business concern is router availability, not data theft. Because the affected firmware is unsupported, normal patch assurance may not exist; replacement or migration planning should be prioritized where deployments are found.
Technical view
CVE-2026-10069 affects an unknown function in usr/sbin/miniupnpd in Shibby Tomato 1.28. The reported weakness is resource consumption, mapped to CWE-400 and CWE-404. CVSS v4.0 is 8.7 with network attack vector, low complexity, no privileges, no user interaction, and high availability impact only.
Likely exposure
Exposure is likely limited to organizations still running Shibby Tomato 1.28 on routers or embedded network devices. Risk is higher where miniupnpd or UPnP behavior is reachable from untrusted networks. The source states the affected product is unsupported and superseded by FreshTomato.
Exploitation context
The source bundle says remote attack is possible, but does not provide evidence of active exploitation. CISA KEV status is false in the provided data. Public references include VulDB, a VulDB CTI page, a submission entry, and a Gitee issue.
Researcher notes
Evidence is sparse. The affected function is not identified, and the provided sources do not name a vendor patch, fixed version, exploit artifact, or operational workaround. Keep analysis constrained to Shibby Tomato 1.28 miniupnpd resource exhaustion unless new authoritative guidance appears.
Mitigation direction
Inventory routers and appliances for Shibby Tomato 1.28 firmware.
Prioritize replacing unsupported Shibby Tomato deployments with supported firmware or hardware.
Check FreshTomato and device-vendor guidance before migration or configuration changes.
Restrict untrusted network reachability to affected router management and service surfaces.
Monitor affected devices for resource exhaustion, service restarts, or availability degradation.
Validation and detection
Confirm whether any devices report Shibby Tomato 1.28.
Verify whether miniupnpd or UPnP functionality is enabled on affected devices.
Review network exposure for affected devices from untrusted segments.
Check device health logs for unexplained resource exhaustion or restarts.
Document remediation status for every identified legacy device.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.