dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-15546

MEDIUM · 6.3 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 →
69/100
Remediation priority · Elevated
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 security flaw has been discovered in Shibby Tomato up to 1.28.0000. Affected by this issue is the function sub_2D568 of the component start_jffs2. Performing a manipulation of the argument jffs2_exec results in os command injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. 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 · moderate confidence

OS command injection vulnerability in Shibby Tomato firmware (up to 1.28.0000) in the start_jffs2 component's sub_2D568 function. The jffs2_exec parameter is not properly sanitized before being passed to the operating system, allowing an attacker to inject arbitrary shell commands. The vulnerability is remotely exploitable and public exploits exist.

MitigationReplace Shibby Tomato with FreshTomato (its successor) which does not contain this vulnerability. If replacement is not feasible, isolate affected devices on network segments with strict access controls to reduce exploitability.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 vendor and version
    Access the router's web interface or check /proc/version or nvram settings to determine the exact firmware version. Look for 'Shibby Tomato' branding and note the version number (e.g., 1.28.0000).
    Affected if The firmware is Shibby Tomato version 1.28.0000 or earlier
  2. Confirm the firmware is not FreshTomato
    Check the firmware name/string in the admin interface or system information page. FreshTomato is the patched successor and is NOT affected by this vulnerability.
    Affected if The firmware identifies as 'Shibby Tomato' rather than 'FreshTomato'
  3. Verify if jffs2 functionality is enabled
    Check the router's configuration for jffs2-related settings, typically found under Administration > JFFS2 or similar admin sections. Look for enable/disable toggles for jffs2 partition mounting.
    Affected if jffs2 is enabled on the device
  4. Inspect jffs2_exec parameter configuration
    Examine the jffs2_exec parameter in the router's NVRAM or configuration file. This parameter specifies commands executed at jffs2 mount time and is the injection point.
    Affected if The jffs2_exec parameter is populated with any value (even empty values may indicate the feature is configured)

The device is affected if it runs Shibby Tomato firmware version 1.28.0000 or earlier with jffs2 enabled and the jffs2_exec parameter present in the configuration.

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

Replace Shibby Tomato with FreshTomato (its successor) which does not contain this vulnerability. If replacement is not feasible, isolate affected devices on network segments with strict access controls to reduce exploitability.

Recommended fix Moderate confidence

FreshTomato (successor to Shibby Tomato - obtain latest stable release for your router model)

  1. 1. Identify the current Shibby Tomato version installed on the affected device
  2. 2. Migrate to FreshTomato, the successor project of Shibby Tomato, as Shibby Tomato is noted as superseded
  3. 3. Obtain the appropriate FreshTomato firmware for your specific router model from the official FreshTomato repository
  4. 4. Backup current router configuration
  5. 5. Flash the FreshTomato firmware following standard firmware upgrade procedures for your device
  6. 6. After upgrade, verify the start_jffs2 functionality works correctly and the command injection vulnerability is resolved
Caveat Router firmware flashing carries risk of brick; ensure compatible firmware for exact router model; configuration migration may require manual reconfiguration

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

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-15546 — 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-15546 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