dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-10870

HIGH · 7.2 CVSS v3.1 Published 2026-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
A flaw has been found in Shibby Tomato 1.28.0000. This affects the function start_dhcpc of the file /sbin/rc of the component Web UI. This manipulation causes os command injection. It is possible to initiate the attack remotely. The exploit has been published and may be used. This project is superseded by FreshTomato.

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 confidence

OS command injection vulnerability in the Web UI of Shibby Tomato 1.28.0000 firmware, specifically in the start_dhcpc function within /sbin/rc, allowing remote attackers to execute arbitrary operating system commands.

MitigationSince Shibby Tomato is unmaintained and superseded by FreshTomato, upgrade to FreshTomato if the hardware is supported, otherwise replace with a currently supported router/firmware to eliminate this vulnerability.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router firmware
    Access the router's Web UI status page or check via telnet/SSH using 'nvram get tomato软件版本' or 'cat /proc/version' to confirm the firmware name and version
    Affected if If the device is running Shibby Tomato version 1.28.0000 specifically
  2. Verify the Web UI is accessible
    Check if the router's Web interface (HTTP/HTTPS on ports 80/443) is reachable from a network outside the local LAN, or review the router's 'Administration > Access Restriction' settings
    Affected if If the Web UI is exposed to untrusted/external networks (not limited to LAN only)
  3. Confirm the vulnerable script exists
    Access the router via telnet/SSH and inspect the script file: grep -n 'start_dhcpc' /sbin/rc to locate the function, then examine how it handles input
    Affected if If /sbin/rc contains a start_dhcpc function that processes user-supplied input without proper sanitization
  4. Check remote management settings
    Review the router's Web UI configuration under Administration > Access Restriction to see if 'Allow remote access' or similar options are enabled
    Affected if If remote management/remote Web UI access is enabled and the management interface is not restricted to trusted IP addresses only

The environment is affected if the router runs Shibby Tomato 1.28.0000 AND the Web UI is accessible from untrusted networks, exposing the vulnerable start_dhcpc function in /sbin/rc to remote attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since Shibby Tomato is unmaintained and superseded by FreshTomato, upgrade to FreshTomato if the hardware is supported, otherwise replace with a currently supported router/firmware to eliminate this vulnerability.

Recommended fix Moderate confidence

FreshTomato (latest stable release - the maintained fork of Shibby Tomato)

  1. Identify your router model to ensure FreshTomato supports your hardware
  2. Download the appropriate FreshTomato firmware for your router from the official FreshTomato website
  3. Access your router's web administration interface
  4. Navigate to Administration > Firmware Upgrade (or similar)
  5. Upload and install the FreshTomato firmware
  6. After reboot, verify the router is running FreshTomato and test network functionality
  7. Restore any custom configurations as needed
Caveat Router firmware replacement; ensure FreshTomato supports your specific router model before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10870 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10870 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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