A denial-of-service security issue exists within RSLinx® Classic. The security issue stems from improper handling of a malformed packet. A crafted CIP packet can cause the RSLinx® Classic service to crash, requiring a restart of the service to recover
Security readout for executives and security teams
Plain-English summary
RSLinx Classic 4.50 and earlier can be forced offline by a malformed network packet. The service crashes and must be restarted, potentially disrupting industrial communications and dependent operations. The supplied record rates this issue critical, although it describes an availability impact rather than data theft or modification.
Executive priority
Treat as an urgent availability risk for exposed or operationally critical installations. Prioritize discovery, segmentation, and vendor-directed remediation, especially where a service outage could interrupt production, monitoring, or industrial communications. The evidence does not support claiming data compromise or active exploitation.
Technical view
CVE-2026-9621 is an unauthenticated, network-reachable denial-of-service vulnerability caused by improper handling of a crafted CIP packet. The supplied record maps it to CWE-190 and assigns CVSS 4.0 score 9.2. Successful triggering crashes the RSLinx Classic service; recovery requires restarting it.
Likely exposure
Exposure is most likely where RSLinx Classic 4.50 or earlier can receive CIP traffic from untrusted or weakly segmented networks. Actual risk depends on deployed versions, network reachability, and the operational importance of services relying on RSLinx Classic.
Exploitation context
The supplied sources do not establish active exploitation, and the bundle marks the CVE as absent from KEV. The reported attack requires no privileges or user interaction and has low complexity, but no exploit availability or observed campaign evidence is provided.
Researcher notes
The record identifies malformed CIP packet handling and CWE-190 but provides limited root-cause detail. CVSS indicates network access, low complexity, no privileges, and no user interaction, with high availability impact. Researchers should avoid production testing; the supplied evidence does not specify affected components beyond RSLinx Classic or name a confirmed fix.
Mitigation direction
Inventory RSLinx Classic installations and identify systems running version 4.50 or earlier.
Check Rockwell Automation advisory SD1794 for the vendor-approved remediation or supported upgrade path.
Restrict CIP access to explicitly authorized management and industrial network segments.
Monitor service availability and prepare controlled restart procedures for affected operational environments.
Validation and detection
Confirm installed RSLinx Classic versions using trusted asset-management or host records.
Review firewall paths and segmentation controls governing CIP access to affected hosts.
Verify unauthorized networks cannot reach the RSLinx Classic service.
Check logs and monitoring history for unexplained RSLinx Classic crashes or restarts.
Validate vendor remediation in a representative environment without sending malformed packets.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.