CVE-2025-9036: Rockwell Automation FactoryTalk® Action Manager · Information Exposure
Affects Rockwell Automation FactoryTalk® Action ManagerSource CVE Database V5
Not known to be exploited · CVSS 8.5 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Aug 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 FactoryTalk® Action Manager | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Immediately restrict network access to FactoryTalk® Action Manager systems by enforcing strict network segmentation and isolating OT networks from general IT and internet-facing networks. 2) Monitor WebSocket traffic locally and on internal networks for unusual token broadcasts or unauthorized connections. 3) Employ endpoint security solutions to detect and prevent unauthorized local clients from listening on network connections. 4) Enforce multi-factor authentication and strong access controls on FactoryTalk® Action Manager interfaces to reduce the impact of token compromise. 5) Conduct internal audits to identify all instances of FactoryTalk® Action Manager version 1.0.0 or below and plan for rapid upgrade once patches become available. 6) Educate users about the risks of interacting with untrusted local applications that could capture tokens. 7) Implement network intrusion detection systems (NIDS) tuned to detect anomalies in WebSocket communications. 8) Collaborate with Rockwell Automation support channels to obtain updates on patch releases and apply them promptly. These measures go beyond generic advice by focusing on network architecture, monitoring, and user awareness tailored to the specific token exposure mechanism.
Description
A security issue in the runtime event system allows unauthenticated connections to receive a reusable API token. This token is broadcasted over a WebSocket and can be intercepted by any local client listening on the connection.