dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10066

HIGH · 8.8 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 security vulnerability has been detected in Shibby Tomato up to 1.28. This issue affects the function sub_9068 of the file tomatoups.cgi of the component UPS Service. The manipulation leads to stack-based buffer overflow. The attack can 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 confidence

A stack-based buffer overflow vulnerability exists in the UPS Service component (tomatoups.cgi) of Shibby Tomato firmware up to version 1.28. The overflow occurs in function sub_9068 and can be exploited remotely via specially crafted input to the UPS service, potentially allowing arbitrary code execution.

MitigationSince Shibby Tomato is end-of-life and superseded by FreshTomato, the recommended remediation is to migrate to FreshTomato or replace affected hardware with currently supported firmware. If the legacy system must remain operational, network segmentation and disabling the UPS service can reduce exposure.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 firmware version and variant
    Check the running firmware version in the router's web interface under Administration > System or via the command line (nvram get firmwarever or cat /proc/version). Confirm it is Shibby Tomato and note the version number.
    Affected if The firmware is Shibby Tomato version 1.28 or any earlier version.
  2. Confirm the UPS Service component is active
    In the router's web interface, navigate to the UPS settings page (usually under Basic > Network or USB/Storage). Verify if the UPS service is configured or enabled.
    Affected if The UPS Service is enabled or configured on the device.
  3. Verify the CGI interface is accessible
    Attempt to access the endpoint /tomatoups.cgi on the router's local IP (e.g., http://192.168.1.1/tomatoups.cgi). A successful HTTP response indicates the affected CGI script is present.
    Affected if The /tomatoups.cgi endpoint responds with any content (indicating it exists and is accessible).

You are affected if your device runs Shibby Tomato firmware version 1.28 or earlier, the UPS Service is enabled, and the /tomatoups.cgi interface is accessible on your network.

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 end-of-life and superseded by FreshTomato, the recommended remediation is to migrate to FreshTomato or replace affected hardware with currently supported firmware. If the legacy system must remain operational, network segmentation and disabling the UPS service can reduce exposure.

Recommended fix Moderate confidence

FreshTomato (latest stable release)

  1. 1. Identify all devices or systems currently running Shibby Tomato firmware.
  2. 2. Download the latest stable FreshTomato release from the official FreshTomato project (as Shibby Tomato is discontinued and superseded by FreshTomato).
  3. 3. Review FreshTomato release notes to confirm the vulnerability has been addressed in the version you plan to use.
  4. 4. Backup current Shibby Tomato configuration if applicable.
  5. 5. Flash/upgrade each affected device from Shibby Tomato to the FreshTomato firmware.
  6. 6. After upgrade, verify the UPS service functionality works correctly in FreshTomato.
  7. 7. Confirm the tomatoups.cgi component no longer contains the vulnerable sub_9068 function or has been patched.
Caveat FreshTomato is a different firmware fork - configuration migration may not be direct; review FreshTomato compatibility with your hardware 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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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