Overview
The cybersecurity world has recently been alerted to a significant vulnerability concerning various models of Linksys devices. This vulnerability, known as CVE-2025-9355, was identified within the scheduleAdd function of the /goform/scheduleAdd file. These particular models are widely used, and the security flaw could potentially lead to a devastating system compromise or data leakage. The gravity of the situation is further accentuated by the fact that the exploit has been made public, and the vendor, after being informed, has not yet responded with a solution.
Vulnerability Summary
CVE ID: CVE-2025-9355
Severity: High (CVSS: 8.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise or data leakage
Affected Products
Escape the Surveillance Era
Most apps won’t tell you the truth.
They’re part of the problem.
Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.
Ameeba Chat gives you a way out.
- • No phone number
- • No email
- • No personal info
- • Anonymous aliases
- • End-to-end encrypted
Chat without a trace.
Product | Affected Versions
Linksys RE6250 | 1.0.013.001
Linksys RE6300 | 1.0.04.001
Linksys RE6350 | 1.0.04.002
Linksys RE6500 | 1.1.05.003
Linksys RE7000 | 1.2.07.001
Linksys RE9000 | 1.0.013.001
How the Exploit Works
The vulnerability resides in the scheduleAdd function of Linksys devices. More specifically, it is a stack-based buffer overflow vulnerability which occurs when the ruleName argument is manipulated. The exploit can be carried out remotely and does not require any user interaction or privileges, which significantly increases its potential impact. Once exploited, the attacker could potentially gain full control of the system, leading to the compromise of sensitive data or even the entire network.
Conceptual Example Code
Here is a conceptual example of how the vulnerability might be exploited. The malicious payload in this case would be designed to overflow the buffer and execute shellcode:
POST /goform/scheduleAdd HTTP/1.1
Host: target.example.com
Content-Type: application/json
{ "ruleName": "A"*5000 } /* Overly long ruleName to trigger buffer overflow */Mitigation Guidance
As of now, the vendor has not provided a patch to fix this vulnerability. Therefore, users are advised to protect their devices using a Web Application Firewall (WAF) or Intrusion Detection System (IDS) as a temporary mitigation. Regularly monitor the vendor’s website for any updates regarding a patch. Additionally, users can also consider disabling the vulnerable function if it is not essential to their operations.