CVE-2026-10872
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 was found in Shibby Tomato 1.28.0000. This issue affects the function start_vpnserver of the file /sbin/rc of the component Web UI. Performing a manipulation results in os command injection. The attack can be initiated remotely. The exploit has been made public and could 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 confidenceOS command injection vulnerability in Shibby Tomato 1.28.0000 Web UI's start_vpnserver function in /sbin/rc allows remote attackers to execute arbitrary operating system commands via manipulated input to the VPN server configuration.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify firmware vendor and versionAccess the router's Web UI status page or run 'nvram get firmver' via SSH/telnet. Look for 'Shibby' as the vendor and confirm version 1.28.0000.Affected if The firmware is Shibby Tomato version 1.28.0000 exactly
-
Locate the vulnerable function in /sbin/rcAccess the router via SSH/telnet and inspect the file /sbin/rc. Search for the 'start_vpnserver' function definition within this file.Affected if The start_vpnserver function exists in /sbin/rc (vulnerable code location)
-
Verify VPN server configuration accessLog into the Web UI and navigate to VPN Server settings, or run 'nvram get vpn_server_enable' to check if VPN server functionality is accessible.Affected if VPN server configuration is accessible in the Web UI (attack vector)
-
Confirm Web UI is network-accessibleAttempt to access the Tomato Web UI from a remote host on the network (typically ports 80 or 443). Check if remote management is enabled via 'nvram get http_remote' or similar.Affected if The Web UI is exposed beyond localhost (remote attack possible)
The environment is affected if it runs Shibby Tomato 1.28.0000 with the start_vpnserver function in /sbin/rc and the Web UI VPN configuration page is accessible.
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 dataApply vendor patch if available; otherwise migrate to FreshTomato (the supported successor) or implement input validation/sanitization in the start_vpnserver function to prevent shell metacharacter injection.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10872 — 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-10872 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