CVE-2026-9624 is a denial-of-service vulnerability in Rockwell Automation RSLinx Classic caused by insufficient validation of data length in Common Industrial Protocol (CIP) packet handling. A remotely supplied crafted CIP packet can cause the RSLinx Classic service to crash. The service must be restarted to restore operation.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability affecting Rockwell Automation RSLinx Classic; no technical impact details are provided in the content.
A denial-of-service vulnerability in RSLinx Classic in which insufficient validation of CIP packet data length permits a crafted CIP packet to crash the service, requiring a service restart.
A high-severity remotely exploitable denial-of-service vulnerability in Rockwell Automation RSLinx Classic. Insufficient validation of crafted CIP packet data length can crash the RSLinx Classic service, requiring a service restart.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.