# CVE-2026-16096: Shibby Tomato webmon_recent_domains sub_40BB50 stack-based overflow

> Remote attackers can exploit a stack-based buffer overflow in Shibby Tomato firmware to execute arbitrary code, requiring migration to FreshTomato.

- **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:** 22 Jul 2026
- **Also known as:** GHSA-3pw4-v8p8-wpvg

## What is CVE-2026-16096?

CVE-2026-16096 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 has been found in Shibby Tomato 1.28 RT-N5x MIPSR2 Build 124. This affects the function sub_40BB50 of the file /proc/webmon_recent_domains. The manipulation leads to stack-based buffer overflow. It is possible to initiate 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-16096?


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

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

## Is CVE-2026-16096 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16096 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16096 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16096 exists.

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-16096/ (Markdown: https://insights.sbomify.com/CVE-2026-16096/index.md)
```

## Sources

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

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