CVE-2025-9178: Rockwell Automation 1715-AENTR EtherNet/IP Adapter · Out-of-bounds Write
Affects Rockwell Automation 1715-AENTR EtherNet/IP AdapterSource CVE Database V5
Not known to be exploited · CVSS 7.7 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% 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:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Rockwell Automation 1715-AENTR EtherNet/IP Adapter | Affected
| Fixed in– |
AI-suggested
1. Implement strict network segmentation to isolate EtherNet/IP adapters from untrusted networks, limiting exposure to potential attackers. 2. Deploy industrial firewalls and intrusion detection/prevention systems (IDS/IPS) capable of monitoring and filtering CIP traffic to detect and block malformed or suspicious payloads. 3. Restrict network access to the 1715-AENTR adapters by enforcing access control lists (ACLs) and limiting management interfaces to trusted hosts only. 4. Establish continuous monitoring and logging of CIP communication to identify anomalies indicative of exploitation attempts. 5. Develop and test automated device restart procedures to minimize downtime in case of a DoS event. 6. Engage with Rockwell Automation for firmware updates or patches as soon as they become available and prioritize timely deployment. 7. Conduct regular security assessments and penetration testing of OT networks to identify and remediate similar vulnerabilities. 8. Train OT personnel on recognizing and responding to network disruptions potentially caused by this vulnerability. 9. Consider deploying network segmentation gateways or protocol-aware proxies that can sanitize CIP traffic before it reaches vulnerable devices.
Description
A denial-of-service security issue exists in the affected product and version. The security issue is caused through CIP communication using crafted payloads. The security issue could result in no CIP communication with 1715 EtherNet/IP Adapter.A restart is required to recover.