Command InjectionWeakness · CWE-77

CVE-2026-10871

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

NVD · unedited

A vulnerability has been found in Shibby Tomato 1.28.0000. This vulnerability affects the function start_6rd_tunnel of the file /sbin/rc of the component Web UI. Such manipulation of the argument ipv6_6rd_borderrelay leads to os command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. This project is superseded by FreshTomato.

Technical summary

dbcve analysis · high confidence

OS command injection vulnerability in Shibby Tomato 1.28.0000 Web UI allows remote attackers to execute arbitrary commands via the ipv6_6rd_borderrelay argument passed to the start_6rd_tunnel function in /sbin/rc. The argument is not properly sanitized before being used in a system call.

MitigationUpgrade to FreshTomato (the successor project) which should contain patched code, or if continued use of Shibby Tomato is required, apply input validation/sanitization to the ipv6_6rd_borderrelay parameter in the start_6rd_tunnel function to prevent command injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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?

dbcve checks

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

Identify Shibby Tomato firmware

Check the router's web interface status page or run 'nvram get ttomato_version' via SSH/telnet to confirm the firmware name and version

Affected if The firmware is Shibby Tomato version 1.28.0000 specifically
Verify IPv6 6rd tunnel configuration

Access the router's Web UI and navigate to the IPv6 configuration section; check if 6rd tunnel is enabled or if the ipv6_6rd_borderrelay parameter is set. Alternatively, run 'nvram get ipv6_6rd_borderrelay' via CLI to see the current value

Affected if The IPv6 6rd tunnel feature is enabled or the ipv6_6rd_borderrelay parameter contains a value (is not empty)
Confirm Web UI accessibility

Attempt to access the router's Web UI from the network. Check if the Web interface is listening on HTTP/HTTPS ports (typically 80/443)

Affected if The Web UI is accessible remotely (not limited to localhost only) and the router is exposed to the network

A system is affected if it runs Shibby Tomato 1.28.0000, has IPv6 6rd tunnel feature configured (ipv6_6rd_borderrelay parameter is set), and has the Web UI accessible to network attackers.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade to FreshTomato (the successor project) which should contain patched code, or if continued use of Shibby Tomato is required, apply input validation/sanitization to the ipv6_6rd_borderrelay parameter in the start_6rd_tunnel function to prevent command injection.

Recommended fix High confidence

FreshTomato (latest stable release - the successor to Shibby Tomato)

1. Backup current router configuration before any firmware changes
2. Download the latest FreshTomato firmware from the official FreshTomato project (as Shibby Tomato is no longer maintained)
3. Access the router's web interface and navigate to Administration > Firmware Upgrade
4. Upload the FreshTomato firmware file and allow the upgrade process to complete
5. After reboot, verify the router is running FreshTomato and reconfigure any custom settings
6. Confirm the ipv6_6rd_borderrelay functionality is no longer present or has been re-implemented securely in FreshTomato

Caveat FreshTomato has a different interface and may require reconfiguration of all custom settings; not all Shibby Tomato features may be available

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

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation6.0 h
Testing4.0 h
Review / QA2.0 h

16.0 hours of engineering $2,840

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-10871 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-10871?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 7.2 High

Exploit likelihood EPSS, next 30 days 2.2%

Remediation

A high-priority fix

Have this fixed 16 hrs · Moderate

Typical engagement from $2,840

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-10871 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References