CVE-2026-16097

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-18. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

July 18, 2026

Last Modified

July 20, 2026

Advisory Details (1)

Auto-updated Jul 18, 2026
No patch confirmed yet.
generic

Stack buffer overflow and command injection risk in Tomato firmware `sbin/rc` scheduler function `sub_42537C` · Issue #IJTQ5U · 王丰毅/CVE - Gitee.com

https://gitee.com/Fengyi-Wang/CVE/issues/IJTQ5U

Vendor Advisories for CVE-2026-16097(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:13 UTCEPSS rescore
  2. 2026-07-27 10:29 UTCGHSA enrichment
  3. 2026-07-26 22:53 UTCEG score recompute
  4. 2026-07-26 22:53 UTCGHSA enrichment
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 11:17 UTCEG score recompute
  8. 2026-07-26 11:17 UTCGHSA enrichment
  9. 2026-07-25 14:17 UTCEPSS rescore
  10. 2026-07-24 14:17 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 03:05 UTCEG score recompute
  13. 2026-07-23 00:08 UTCEG score recompute
  14. 2026-07-23 00:08 UTCGHSA enrichment
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-21 15:24 UTCEPSS rescore
  17. 2026-07-20 17:53 UTCEG score recompute
  18. 2026-07-20 17:53 UTCGHSA enrichment
  19. 2026-07-20 17:08 UTCEPSS rescore
  20. 2026-07-19 14:30 UTCEPSS rescore
  21. 2026-07-18 14:07 UTCEG score recompute
  22. 2026-07-18 14:06 UTCGHSA enrichment
  23. 2026-07-18 12:14 UTCEG score recompute
  24. 2026-07-18 12:14 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16097?
CVE-2026-16097 is a high vulnerability published on July 18, 2026. 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…
When was CVE-2026-16097 disclosed?
CVE-2026-16097 was first published in the National Vulnerability Database on July 18, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16097 actively exploited?
CVE-2026-16097 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.4% of all scored CVEs.
What is the CVSS score of CVE-2026-16097?
CVE-2026-16097 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-16097?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16097, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16097

Explore →

Is Your Infrastructure Affected by CVE-2026-16097?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs