CVE-2025-7350: Rockwell Automation Stratix IOS · Injection
Affects Rockwell Automation Stratix IOSSource CVE Database V5
Not known to be exploited · CVSS 8.6 High.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Rockwell Automation Stratix IOS | Affected
| Fixed in– |
AI-suggested
- Immediate network segmentation: Isolate Stratix devices from general IT networks and restrict access to trusted management stations only.
- Implement strict access controls and monitoring: Use network intrusion detection systems (NIDS) and anomaly detection tailored for industrial protocols to identify suspicious configuration uploads or unusual device behavior.
- Employ multi-factor authentication (MFA) for all management interfaces to reduce the risk of unauthorized access, even though the vulnerability does not require authentication, this limits other attack vectors.
- Disable or restrict remote configuration upload capabilities where possible until patches are available.
- Maintain up-to-date inventory and asset management to quickly identify affected devices and prioritize remediation.
- Engage with Rockwell Automation for timely patch releases and apply updates as soon as they become available.
- Conduct regular security awareness training focused on phishing and social engineering to mitigate the user interaction requirement.
- Use network-level filtering to block known malicious IP addresses and restrict outbound connections from Stratix devices to only necessary endpoints.
- Implement logging and audit trails for configuration changes to enable rapid incident response and forensic analysis.
Description
A security issue affecting multiple Cisco devices also directly impacts Stratix® 5410, 5700, and 8000 devices. This can lead to remote code execution by uploading and running malicious configurations without authentication.