# CVE-2026-16095: Shibby Tomato rc setup_conntrack out-of-bounds write

> Remote attackers can trigger an out-of-bounds write in Shibby Tomato firmware, potentially leading to code execution on affected routers.

- **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-6jfj-qh5w-m9vr

## What is CVE-2026-16095?

CVE-2026-16095 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 flaw has been found in Shibby Tomato 1.28 RT-N5x MIPSR2 Build 124. Affected by this issue is the function setup_conntrack of the file /sbin/rc. Executing a manipulation of the argument ct_tcp_timeout can lead to out-of-bounds write. The attack may be performed from remote. This project is superseded by FreshTomato.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-16095 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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