dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10067

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 vulnerability was detected in Shibby Tomato 1.28. Impacted is the function sub_90F0 of the file multimon.cgi. The manipulation results in stack-based buffer overflow. The attack can be launched 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 vulnerability in the sub_90F0 function of multimon.cgi in Shibby Tomato 1.28 firmware, allowing remote exploitation via crafted input to the web interface component.

MitigationMigrate to FreshTomato (the supported successor project) or replace affected hardware with currently supported equipment, as Shibby Tomato 1.28 is no longer maintained.

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 the router firmware version
    Access the router's web administrative interface and look for the firmware version in the status or administration page, or run 'cat /proc/version' or 'uname -a' via SSH/telnet if available
    Affected if The firmware shows Shibby Tomato version 1.28 exactly
  2. Confirm the firmware is Shibby Tomato (not FreshTomato)
    Check the firmware name/version string in the router's status page or via 'nvram get tomatowebversion' or 'nvram get os_version' command
    Affected if The firmware identifies as Shibby Tomato rather than FreshTomato
  3. Check if multimon.cgi is accessible
    Attempt to access the multimon.cgi script via HTTP/HTTPS request to the router (e.g., http://router-ip/cgi-bin/multimon.cgi)
    Affected if The CGI script responds or is reachable on the network
  4. Verify multimon functionality is enabled
    Check router configuration for multimon settings, or look for multimon-related entries in the NVRAM variables via 'nvram show | grep multimon'
    Affected if Multimon feature or module is enabled on the device

A user is affected if the router runs Shibby Tomato 1.28 firmware with the multimon.cgi feature accessible and enabled on the 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Migrate to FreshTomato (the supported successor project) or replace affected hardware with currently supported equipment, as Shibby Tomato 1.28 is no longer maintained.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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