CVE-2026-108896: Linksys E1700 OS command injection in IPv6 configuration

CVE-2026-108896 · Severity: critical · CVSS 9.9 · Published 2026-10-12

The Linksys E1700 router contains a remote command injection vulnerability in its IPv6 configuration handler that allows attackers to execute arbitrary operating system commands without authentication. An attacker on the network can craft a malicious request to the router's web interface to gain complete control of the device, enabling data theft, network compromise, or use as a launching point for further attacks.

Technologies: Linksys E1700. Vendors: Linksys.

Quick answers

Is CVE-2026-108896 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-108896 being exploited in the wild.
How severe is CVE-2026-108896?
Critical severity, with a CVSS score of 9.9, published 12 October 2026.
Which products and versions are affected?
Linksys E1700 1.0.0.4.003.
Is there a fix for CVE-2026-108896?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-108896 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-108896?
Check whether you run Linksys E1700 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The setLinksysIpv6 function in the /goform/setLinksysIpv6 endpoint fails to sanitize the _6rd_prefix and _6rd_prefix_len parameters before passing them through the ipv6cmd binary, leading to OS command injection. The vulnerability is network-accessible and requires no authentication; an attacker can inject shell commands (e.g., via backticks) that are executed with router privileges.

Affected products

  • Linksys E1700 1.0.0.4.003

Timeline

  • 2026-10-12: disclosed: Vulnerability disclosed publicly on GitHub; vendor did not respond to early disclosure attempt

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.