CVE-2026-10069
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA resource consumption vulnerability exists in the miniupnpd component of Shibby Tomato 1.28 firmware, exploitable remotely leading to denial of service conditions. The specific vulnerable function within usr/sbin/miniupnpd is not detailed in available sources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the firmware versionCheck the router's web interface status page or run 'nvram get firmver' or 'cat /proc/version' to confirm the firmware is Shibby Tomato version 1.28Affected if The device is running Shibby Tomato 1.28 firmware
-
Verify miniupnpd binary existsCheck if the file /usr/sbin/miniupnpd exists on the device using 'ls -la /usr/sbin/miniupnpd'Affected if The miniupnpd binary is present on the system
-
Confirm UPnP service is enabledCheck the router's web UI under 'USB and NAS' or 'Advanced' > 'UPnP' settings, or run 'nvram get upnp_enable' to see if UPnP is turned onAffected if UPnP is enabled and the service is active
-
Check if miniupnpd process is runningRun 'ps | grep miniupnpd' or 'pidof miniupnpd' to see if the daemon is currently executingAffected if The miniupnpd process is running on the device
-
Assess network exposure of UPnPCheck router firewall rules or run 'iptables -L -n | grep 1900' to see if UDP port 1900 (UPnP SSDP) is exposed to WANAffected if UPnP ports are accessible from the WAN/Internet side
The device is affected if it runs Shibby Tomato 1.28 with miniupnpd present, UPnP enabled, and the service is active or exposed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince Shibby Tomato 1.28 is end-of-life and no longer maintained, migrate to FreshTomato (the supported successor) or replace affected hardware with a currently supported alternative.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10069 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10069 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data