dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-15545

HIGH · 8.8 CVSS v3.1 Published 2026-07-13
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 5 weeks old

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 identified in Shibby Tomato up to 1.28.0000. Affected by this vulnerability is the function main of the file www/apcupsd/tomatodata.cgi of the component apcupsd. Such manipulation leads to out-of-bounds write. The attack may be launched remotely. The exploit is publicly available and might 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 · high confidence

Out-of-bounds write vulnerability in the main function of the apcupsd CGI component (www/apcupsd/tomatodata.cgi) in Shibby Tomato router firmware up to v1.28.0000. This allows remote attackers to write data beyond allocated memory boundaries, potentially leading to code execution or denial of service.

MitigationUpgrade to FreshTomato or a patched firmware version to address the out-of-bounds write in the apcupsd CGI component; the vulnerable tomatodata.cgi file should be removed or updated if staying on Shibby Tomato.

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 firmware version
    Access the router's web interface and look for the version information, typically found in the status or administration page. Alternatively, check the system log or use the command line if accessible.
    Affected if The firmware is Shibby Tomato and the version is 1.28.0000 or lower.
  2. Confirm apcupsd CGI is present
    Locate the tomatodata.cgi file on the router's web filesystem. This is typically found in the /cgi-bin/ or /web/ directory of the web interface.
    Affected if The file tomatodata.cgi exists in the web CGI directory.
  3. Verify apcupsd feature is enabled
    Check the Shibby Tomato web interface under the "UPS" or "apcupsd" settings section to see if the UPS monitoring feature is turned on.
    Affected if The apcupsd or UPS monitoring feature is enabled and serving the CGI.
  4. Check web interface exposure
    Review the router's firewall settings or network configuration to determine if the web management interface is accessible from the WAN (remote) side.
    Affected if The web interface (port 80/443) is exposed to untrusted networks or the internet.

A system is affected if it runs Shibby Tomato version 1.28.0000 or lower, has the apcupsd CGI (tomatodata.cgi) present and enabled, and has its web interface accessible to remote attackers.

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

Upgrade to FreshTomato or a patched firmware version to address the out-of-bounds write in the apcupsd CGI component; the vulnerable tomatodata.cgi file should be removed or updated if staying on Shibby Tomato.

Recommended fix Moderate confidence

FreshTomato (latest stable release)

  1. 1. Identify all deployed instances of Shibby Tomato firmware.
  2. 2. Backup current router configurations before making any changes.
  3. 3. Download the latest FreshTomato firmware from the official FreshTomato project website (https://freshtomato.org/).
  4. 4. Flash the FreshTomato firmware to replace the affected Shibby Tomato installation.
  5. 5. Reconfigure the router settings after flashing, as firmware upgrades may reset configuration.
  6. 6. Verify that the www/apcupsd/tomatodata.cgi functionality works correctly in FreshTomato.
  7. 7. Monitor for any anomalous behavior or continued vulnerability indicators.
Caveat FreshTomato is a different firmware fork with different configuration interfaces; some Shibby Tomato-specific settings may not transfer directly and will need manual reconfiguration.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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