Security readout for executives and security teams
Plain-English summary
CVE-2026-10124 affects unsupported Shibby Tomato router firmware through the RIP daemon. A remote, authenticated or permissioned attacker may trigger a stack buffer overflow that could compromise the device. Public exploit information is reported, but the provided sources do not show confirmed active exploitation.
Executive priority
Treat this as a high-priority legacy router risk. The affected firmware is unsupported, the impact is complete device compromise, and public exploit information exists. Prioritize inventory, isolation, and replacement or migration planning.
Technical view
The issue is a stack-based buffer overflow in rip_zebra_read_ipv4 within /usr/sbin/ripd, under the Zserv Handler component. Shibby Tomato versions 1.0 through 1.28 are listed as affected. CVSS v2 is 9.0 with network access, low complexity, single authentication, and complete confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on routers or embedded network devices still running Shibby Tomato 1.28 or earlier, especially where ripd or Zserv-related routing services are enabled and reachable. The project is no longer maintained, which increases remediation urgency.
Exploitation context
The bundle states the attack can be launched remotely and that exploit details are publicly disclosed. It also marks KEV as false, so there is no source-backed evidence here of active exploitation. The CVSS vector indicates some authentication or permissions are required.
Researcher notes
Evidence is centered on VulDB/CVE metadata and a public issue reference. The bundle does not provide vendor-fixed versions, confirmed exploitation telemetry, or detailed affected device models. Avoid assuming FreshTomato is automatically fixed without checking its guidance.
Mitigation direction
- Identify and retire Shibby Tomato 1.28 or earlier devices.
- Check FreshTomato and vendor guidance before migrating firmware.
- Disable unused RIP/routing services where operationally safe.
- Restrict management and routing-service access to trusted networks.
- Replace unsupported devices if supported firmware is unavailable.
Validation and detection
- Inventory routers for Shibby Tomato firmware versions 1.0 through 1.28.
- Confirm whether /usr/sbin/ripd or RIP services are enabled.
- Review network exposure for routing and management interfaces.
- Check logs for unexpected ripd crashes or restarts.
- Verify compensating access controls restrict untrusted network reachability.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-10124 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR810VulDBCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R2.85.9VulDBCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R2.85.9VulDBCVSS: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:P——VulDBVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: 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:P
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R
Base CVSS 3.0 score
8.8HighVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R
Base CVSS 2.0 score
9CriticalVector: AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineVulDB
Advisory disclosed
- Source timelineVulDB
VulDB entry created
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineVulDB
VulDB entry last update
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- VDB-367301 | Shibby Tomato Zserv ripd rip_zebra_read_ipv4 stack-based overflowCVE reference, VulDB · vdb-entry, technical-description
- VDB-367301 | CTI Indicators (IOB, IOC, IOA)CVE reference, VulDB · signature, permissions-required
- Submit #818239 | Tomato by Shibby Tomato Firmware 1.28 Stack-based Buffer OverflowCVE reference, VulDB · third-party-advisory
- https://gitee.com/Fengyi-Wang/CVE/issues/IJ9FFGCVE reference, VulDB · exploit, issue-tracking
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.