CVE-2026-10068
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 flaw has been found in Shibby Tomato 1.28. The affected element is the function send of the file usr/sbin/miniupnpd of the component SUBSCRIBE Call Handler. This manipulation causes server-side request forgery. The attack may be initiated 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 confidenceServer-Side Request Forgery (SSRF) vulnerability in Shibby Tomato 1.28 firmware's miniupnpd component. The SUBSCRIBE Call Handler's send function allows a remote attacker to induce the device to make arbitrary HTTP requests to internal or external resources, potentially exposing internal services or facilitating further attacks.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 firmware versionAccess the router's web administration interface and look for the firmware version in the Basic/Status page, or run 'cat /proc/version' or 'uname -a' via telnet/SSHAffected if The firmware shows version 1.28 from Shibby Tomato
-
Locate miniupnpd binaryCheck if /usr/sbin/miniupnpd exists on the device by running 'ls -la /usr/sbin/miniupnpd' via telnet/SSHAffected if The file /usr/sbin/miniupnpd exists on the filesystem
-
Verify UPnP service is enabledCheck the router's web interface under Basic > Network or NAT/DHCP settings for UPnP configuration, or run 'ps w | grep miniupnpd' to see if the process is runningAffected if UPnP is enabled and miniupnpd process is running
-
Confirm miniupnpd supports SUBSCRIBERun 'miniupnpd -h' or check the binary for SUBSCRIBE-related strings with 'strings /usr/sbin/miniupnpd | grep -i subscribe'Affected if The miniupnpd binary includes SUBSCRIBE handler functionality
A device is affected if it runs Shibby Tomato 1.28 firmware with the miniupnpd component installed and UPnP SUBSCRIBE functionality enabled, allowing remote attackers to trigger arbitrary HTTP requests via the vulnerability.
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.
dbcve · scopedThis vulnerability affects end-of-life firmware (Shibby Tomato 1.28) which is no longer supported. Migrate to FreshTomato or replace affected hardware with a currently supported router solution.
FreshTomato (latest stable release)
- 1. Identify all devices currently running Shibby Tomato 1.28 firmware
- 2. Migrate devices to FreshTomato, which is the supported successor to Shibby Tomato
- 3. FreshTomato addresses many security issues present in the legacy Shibby Tomato codebase
- 4. If migration to FreshTomato is not immediately feasible, consider disabling the miniupnpd (UPnP) service in Tomato's administration interface to reduce attack surface
- 5. Implement network segmentation to isolate affected devices from untrusted networks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Testing6.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,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10068 — 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-10068 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