Authenticated memory corruption via crafted scheduler name
Published Jul 18, 2026 · Updated Jul 18, 2026
Stack-based buffer overflow in Shibby Tomato 1.28 allows remote authenticated users to corrupt memory through a crafted scheduler name. In sub_42537C, manipulating argument a1 overruns a stack buffer while the Scheduler Name Handler processes the supplied name; the exact write operation is undisclosed. Low-privilege network access is required, and public sources do not demonstrate code execution or exploitation in the wild.
Summary
What happened
Stack-based buffer overflow in Shibby Tomato 1.28 allows remote authenticated users to corrupt memory through a crafted scheduler name. In sub_42537C, manipulating argument a1 overruns a stack buffer while the Scheduler Name Handler processes the supplied name; the exact write operation is undisclosed. Low-privilege network access is required, and public sources do not demonstrate code execution or exploitation in the wild.
The record
- CVE
- CVE-2026-16097
- Published
- Jul 18, 2026
- Updated
- Jul 18, 2026
- Vendor
- Shibby
- Product
- Tomato
- Classifications
- CWE-119, CWE-121, T1210
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 18, 2026CVE publishedPublication date reported by the CVE source.
- Jul 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.28
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo