# CVE-2026-16097: Shibby Tomato Scheduler Name sub_42537C stack-based overflow

> Remote attackers can trigger a stack-based buffer overflow in the scheduler name handler of Shibby Tomato firmware, potentially executing arbitrary code.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-wvq6-2vpm-hch4

## What is CVE-2026-16097?

CVE-2026-16097 is a high-severity memory corruption vulnerability in Shibby Tomato, published on 18 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Shibby Tomato 1.28. This vulnerability affects the function sub_42537C of the component Scheduler Name Handler. The manipulation of the argument a1 results in stack-based buffer overflow. It is possible to launch the attack remotely. This project is superseded by FreshTomato.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-16097?


## How do I fix CVE-2026-16097?

No fix has been published for CVE-2026-16097 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16097 being exploited?

There is no known exploitation of CVE-2026-16097 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16097 and fix it if it is affected.

What it is: CVE-2026-16097 is a high-severity memory corruption vulnerability in Shibby Tomato, published on 18 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16097 in the wild and no public exploit code.

Affected product: Shibby Tomato. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16097/ (Markdown: https://insights.sbomify.com/CVE-2026-16097/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16097
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16097
- OSV: https://osv.dev/vulnerability/CVE-2026-16097

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16097/
Summaries are generated and may contain mistakes; the official description above is the record.