dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10065

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 weakness has been identified in Shibby Tomato 1.28. This vulnerability affects the function get_ups_field of the file tomatodata.cgi. Executing a manipulation of the argument Date can lead to stack-based buffer overflow. It is possible to launch the attack 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

Stack-based buffer overflow in the get_ups_field function of tomatodata.cgi in Shibby Tomato 1.28 allows remote attackers to overflow a stack buffer by manipulating the Date argument, potentially leading to arbitrary code execution.

MitigationSince Shibby Tomato is no longer supported, migrate to FreshTomato or replace the affected device. If immediate migration is not possible, restrict network access to the tomatodata.cgi endpoint as a temporary measure.

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. Confirm Shibby Tomato version
    Access the router's web interface or check the firmware image file for the exact version number. Look for 'Tomato' in the admin dashboard or system information page.
    Affected if The installed version is 1.28 or falls within the Shibby Tomato 1.28 release line
  2. Verify UPS monitoring is enabled
    Log into the router's web interface and navigate to the UPS or Power Management settings section. Check if UPS monitoring functionality is turned on.
    Affected if UPS monitoring is enabled and running on the device
  3. Check for tomatodata.cgi accessibility
    Attempt to access the /tomatodata.cgi endpoint on the router (e.g., http://<router-ip>/tomatodata.cgi). This is the affected CGI binary containing the vulnerable get_ups_field function.
    Affected if The tomatodata.cgi script is accessible and responds to requests
  4. Inspect Date parameter handling
    If UPS monitoring is enabled, examine how the Date parameter is processed by the web interface or captured in logs. The vulnerability is triggered through manipulation of this parameter.
    Affected if The Date parameter can be submitted to tomatodata.cgi and the UPS monitoring feature accepts external input for date-related fields

A device is affected if it runs Shibby Tomato 1.28 with UPS monitoring functionality enabled and the tomatodata.cgi interface is accessible, allowing manipulation of the Date parameter.

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 no longer supported, migrate to FreshTomato or replace the affected device. If immediate migration is not possible, restrict network access to the tomatodata.cgi endpoint as a temporary measure.

Recommended fix Moderate confidence

FreshTomato (latest stable release)

  1. 1. Identify your router model and verify FreshTomato supports it by checking the FreshTomato website or documentation.
  2. 2. Download the appropriate FreshTomato firmware version for your router from the official FreshTomato website.
  3. 3. Access your router's web admin interface (typically http://192.168.1.1).
  4. 4. Navigate to the Administration > Firmware Upgrade section.
  5. 5. Upload and flash the FreshTomato firmware file.
  6. 6. After the router reboots, log into the FreshTomato interface and reconfigure your network settings as needed.
Caveat Migrating from Shibby Tomato to FreshTomato may require reconfiguration of network settings, port forwards, and custom scripts; ensure you backup your current configuration 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-10065 — 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-10065 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