Attack Chain

1. An attacker identifies a Shibby Tomato router running the vulnerable 1.28 RT-N5x MIPSR2 Build 124 firmware that is exposed and accessible on the network.
2. The attacker establishes a network connection to the vulnerable router, potentially requiring low-privileged access based on the CVSS score.
3. The attacker crafts a malicious network packet or request specifically designed to interact with the setup_conntrack function within the /sbin/rc file.
4. The malicious request includes a specially crafted value for the ct_tcp_timeout argument, designed to exceed expected buffer boundaries.
5. Upon processing this manipulated argument, the setup_conntrack function attempts to write data beyond its allocated memory buffer.
6. This out-of-bounds write operation corrupts adjacent memory, potentially overwriting critical data or code pointers within the router's operating system.
7. Depending on the specific memory corruption, this can lead to the router crashing (denial of service) or allow the attacker to execute arbitrary code with the privileges of the affected process, achieving full system compromise.

Impact

Successful exploitation of CVE-2026-16095 can lead to severe consequences for affected organizations. The primary observed impacts include denial of service, where the vulnerable router becomes unresponsive or reboots unexpectedly due to memory corruption. More critically, an attacker could achieve arbitrary code execution, enabling them to gain full control over the router. This level of compromise allows for network reconnaissance, manipulation of network traffic, establishment of persistent backdoors, or use of the router as a pivot point for further attacks into internal networks. The high CVSS score reflects the significant confidentiality, integrity, and availability impacts on the affected device.

Recommendation

• Immediately patch CVE-2026-16095 by updating Shibby Tomato firmware 1.28 RT-N5x MIPSR2 Build 124 to a version where this vulnerability is resolved, or migrate to FreshTomato if a direct patch is unavailable.
• Implement network segmentation to restrict remote access to router administration interfaces.
• Monitor network connection logs from router devices for unusual or malformed requests targeting device administration ports.
• Deploy a firewall to filter or inspect network traffic for anomalies that might indicate attempts to manipulate connection tracking arguments.