CVE-2026-15548
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 security vulnerability has been detected in Shibby Tomato up to 1.28.0000. This vulnerability affects the function sub_407220 of the file /usr/sbin/httpd of the component DNS List Rendering. The manipulation leads to stack-based buffer overflow. The attack is possible to be carried out remotely. This project is superseded by FreshTomato.
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 DNS List Rendering component (/usr/sbin/httpd) of Shibby Tomato firmware up to v1.28.0000 allows remote attackers to potentially execute arbitrary code via malformed DNS list data. The vulnerability exists in function sub_407220 and carries a CVSS 8.8, indicating high severity with network-exploitable impact.
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 the firmware variantCheck the firmware brand/version by logging into the router admin interface or running 'cat /proc/version' or 'nvram get firmver' via SSHAffected if The device runs Shibby Tomato firmware rather than FreshTomato (which has fixed the vulnerability)
-
Check the firmware version numberRun 'nvram get firmver' or 'cat /proc/jffs2/version' via SSH, or view the version in the router's web admin headerAffected if The version is v1.28.0000 or earlier (any version up to and including v1.28.0000 is affected)
-
Verify the httpd binary existsCheck if /usr/sbin/httpd exists on the device by running 'ls -la /usr/sbin/httpd' via SSHAffected if The binary /usr/sbin/httpd exists and is the Shibby Tomato version (vulnerable component)
-
Determine if DNS List feature is configuredCheck router DNS settings in the web interface under Basic > Network or via 'nvram get dhcpd_dns' via SSHAffected if DNS list rendering functionality is enabled or any custom DNS lists are configured (this is the attack vector)
-
Assess network exposure of httpd serviceCheck if httpd listens on WAN/public interfaces via 'netstat -an | grep 80' or review firewall rules in the web interface under Administration > FirewallAffected if The httpd service is exposed to WAN/untrusted networks (enables remote exploitation)
A user is affected if the device runs Shibby Tomato firmware version v1.28.0000 or earlier with the DNS List feature enabled and httpd accessible from untrusted networks.
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 successor project) which addresses this vulnerability; if migration is not immediately feasible, restrict network access to the httpd service and monitor for indicators of compromise.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15548 — 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-15548 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