# CVE-2026-19034: Shibby Tomato qoslimittc_stop.sh new_qoslimit_stop os command injection

> Remote attackers can execute arbitrary OS commands via the wan_iface argument in Shibby Tomato firmware, which is now end-of-life.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-p42c-v74f-mh4c

## What is CVE-2026-19034?

CVE-2026-19034 is a high-severity command injection vulnerability in Shibby Tomato, published on 6 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was determined in Shibby Tomato 1.28.0000. Affected by this vulnerability is the function new_qoslimit_stop of the file /tmp/qoslimittc_stop.sh. Executing a manipulation of the argument wan_iface can lead to os command injection. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. This project is superseded by FreshTomato.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-19034 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19034 is a high-severity command injection vulnerability in Shibby Tomato, published on 6 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19034 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-19034/ (Markdown: https://insights.sbomify.com/CVE-2026-19034/index.md)
```

## Sources

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

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