CVE-2025-8008VulnerabilityPublished 9 Sep 2025

CVE-2025-8008: Rockwell Automation 1756-ENT2R, 1756-EN4TR, 1756-EN4TRXT · Improper Handling of Exceptional Conditions

Affects Rockwell Automation 1756-ENT2R, 1756-EN4TR, 1756-EN4TRXTSource CVE Database V5

Not known to be exploited · CVSS 7.1 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector: Adjacent
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable system is bound to a protocol stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Rockwell Automation 1756-ENT2R, 1756-EN4TR, 1756-EN4TRXT	Affected <=6.001	Fixed in–

AI-suggested

1. Network Segmentation: Isolate the affected Rockwell Automation devices on dedicated network segments with strict access controls to limit exposure to adjacent network attackers. 2. Access Control Lists (ACLs): Implement ACLs on network devices to restrict traffic to and from the affected modules, allowing only trusted management and control systems to communicate with them. 3. Monitoring and Anomaly Detection: Deploy industrial network monitoring tools to detect unusual Forward Close operations or malformed messages targeting these devices. 4. Vendor Coordination: Engage with Rockwell Automation for official patches or firmware updates addressing CVE-2025-8008 and apply them promptly once available. 5. Incident Response Planning: Prepare response procedures for potential DoS incidents affecting these devices to minimize downtime and restore operations quickly. 6. Configuration Review: Review device configurations to disable or limit Forward Close operations if possible or apply any recommended configuration hardening from the vendor. 7. Physical Security: Ensure physical security controls prevent unauthorized access to network ports connected to these devices, reducing the risk of local exploitation.

Description

A security issue exists in the protected mode of EN4TR devices, where sending specifically crafted messages during a Forward Close operation can cause the device to crash.

Impact

For European organizations, especially those operating critical infrastructure, manufacturing plants, or utilities that rely on Rockwell Automation's 1756 series communication modules, this vulnerability presents a substantial risk. A successful exploitation could cause network communication failures between PLCs and control systems, resulting in process interruptions, production downtime, or safety system malfunctions. Given the role of these devices in industrial automation, availability impacts could cascade into broader operational disruptions, financial losses, and potential safety hazards. European industries such as automotive manufacturing, energy production, and chemical processing, which heavily use industrial control systems, could be particularly vulnerable. Additionally, the lack of required authentication and user interaction means that attackers with access to the industrial network segment could exploit this vulnerability remotely, increasing the threat level. Although no exploits are currently known in the wild, the high severity score and ease of exploitation suggest that threat actors may develop attacks targeting this vulnerability, especially in geopolitically sensitive sectors.

CWE-755Improper Handling of Exceptional Conditions (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product does not handle or incorrectly handles an exceptional condition.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

rockwellautomation.com/en-us/trust-center/security-advisories/advisory.SD1739.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Sep 2025, 12:42 UTC

WeaknessesCWE-755

Technical details

References

Community reviews

Related threats