CVE-2026-10124
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was determined in Shibby Tomato up to 1.28. Affected is the function rip_zebra_read_ipv4 of the file /usr/sbin/ripd of the component Zserv Handler. Executing a manipulation can lead to stack-based buffer overflow. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. This project is superseded by FreshTomato. This vulnerability only affects products that are no longer supported by the maintainer.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStack-based buffer overflow in the rip_zebra_read_ipv4 function within the RIP daemon (ripd) Zserv Handler of Shibby Tomato firmware up to v1.28. The vulnerability allows remote attackers to execute arbitrary code via specially crafted RIP packets, potentially compromising the router.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify router firmware typeCheck the router's web interface or run 'cat /proc/version' or 'uname -a' to confirm the device is running Shibby Tomato firmwareAffected if The device is running Shibby Tomato (not FreshTomato or other firmware)
-
Locate the ripd binaryVerify the existence of /usr/sbin/ripd on the router filesystem using 'ls -la /usr/sbin/ripd'Affected if The ripd binary exists at /usr/sbin/ripd indicating the RIP daemon component is present
-
Check if RIP daemon is runningRun 'ps | grep ripd' or check running processes for ripd to determine if the RIP daemon is actively runningAffected if The ripd process is currently running on the device
-
Verify RIP protocol is enabledCheck router web UI under 'Basic > Network' or run 'ripd -v' to see if RIP protocol is enabled and configuredAffected if RIP protocol (IPv4) is enabled in the router configuration, which activates the vulnerable rip_zebra_read_ipv4 function in the Zserv Handler
-
Confirm Zserv Handler configurationCheck ripd configuration files or run 'ripd -h' to see Zserv-related options, as the vulnerability exists in the Zserv Handler component that processes IPv4 packetsAffected if ZSERV or zebra communication is enabled/configured for RIP to communicate with other routing daemons
The environment is affected if the device runs Shibby Tomato with the ripd daemon present and RIP protocol enabled, exposing the rip_zebra_read_ipv4 function in the Zserv Handler to specially crafted IPv4 packets.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataMigrate to FreshTomato (the supported successor) or replace affected devices with supported hardware, as Shibby Tomato is end-of-life. If immediate migration is not possible, isolate affected devices behind firewalls and disable RIP routing where feasible.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10124 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10124 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data