Skip to main content
VulnerabilityPublished Updated

CVE-2026-27849: Linksys MR9600 · OS Command Injection

Affects Linksys MR9600Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
LinksysMR9600Affected
  • =1.0.4.205530
Fixed in–
LinksysMX4200Affected
  • =1.0.13.210200
Fixed in–

AI-suggested

  1. Immediate mitigation should focus on network segmentation: isolate affected Linksys MR9600 and MX4200 devices from critical network segments to limit potential lateral movement.
  2. Implement strict firewall rules to restrict access to the update functionality and mesh network configuration interfaces, allowing only trusted management hosts.
  3. Monitor network traffic for unusual or suspicious activity targeting the TLS-SRP update channels, including unexpected command execution patterns or anomalous connections.
  4. Disable or restrict mesh network update features if feasible until patches are available.
  5. Regularly check Linksys official channels for firmware updates addressing this vulnerability and apply patches promptly once released.
  6. Employ intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics designed to detect OS command injection attempts.
  7. Conduct security audits and penetration testing focused on router management interfaces to identify other potential weaknesses.
  8. Educate network administrators about this vulnerability and encourage vigilance for signs of compromise. These steps go beyond generic advice by focusing on controlling access to the vulnerable update functionality and monitoring for exploitation attempts in the absence of immediate patches.

Description

Due to missing neutralization of special elements, OS commands can be injected via the update functionality of a TLS-SRP connection, which is normally used for configuring devices inside the mesh network. This issue affects MR9600: 1.0.4.205530; MX4200: 1.0.13.210200.

References

Community reviews

Loading reviews…