Key takeaways
- CC-Link IE TSN has at least two Mitsubishi-disclosed, network-exploitable denial-of-service vulnerabilities on record in 2025 and 2026, and neither has a vendor patch.
- That convergence is also the security-relevant part.
- Mitsubishi's advisory is explicit that no fix is planned.
- CVE-2026-13584 is not CC-Link IE TSN's first disclosed vulnerability.
CC-Link IE TSN has at least two Mitsubishi-disclosed, network-exploitable denial-of-service vulnerabilities on record in 2025 and 2026, and neither has a vendor patch. CVE-2026-13584 (CVSS v4.0 7.1) lets an attacker already on a CC-Link IE TSN network send specially crafted packets to tamper with control data and disrupt 35 product categories; CVE-2025-3511 (CVSS v3.1 7.5) lets a remote, unauthenticated attacker crash CC-Link IE TSN Remote I/O and MELSEC iQ-R/iQ-F modules with a single crafted UDP packet. Mitsubishi Electric's own advisory for the newer finding states plainly that no fix is planned — the mitigation is network segmentation and physical access control, not a firmware update.
This guide draws directly on CLPA's own technology page, Mitsubishi Electric's own PSIRT advisory PDF (2026-005), and NVD's published records for both CVEs — each fetched and read for this guide, not paraphrased from a secondary summary. CISA's republication (ICSA-26-211-07) is named for cross-reference; confirm current advisory status directly at cisa.gov before acting on it.
What is CC-Link IE TSN, and why does it matter for OT security?
CC-Link IE TSN is the newest and, per CLPA's own technology page, flagship member of the CC-Link family of industrial network technologies — "the world's first to adopt TSN (Time-Sensitive Networking) technology, which extends the standard Ethernet." It sits at Layer 2 of the OSI reference model, combining the CC-Link IE TSN protocol itself with standard Ethernet protocols at Layers 3 through 7, and uses IEEE 802.1AS for time synchronization (CLPA states accuracy "within ±1 μs") and IEEE 802.1Qbv to schedule time-sliced communication cycles by priority. That combination lets a single physical network carry deterministic motion-control traffic and conventional IT/IIoT traffic side by side — the exact use case CLPA positions it for: accelerating smart-factory and Industrial IoT deployments where OT and IT networks increasingly converge.
That convergence is also the security-relevant part. A protocol engineered to mix deterministic control traffic with general Ethernet traffic on one network inherits attack surface from both worlds: anything already reachable from a compromised IT segment is now, by design, closer to the controllers, servos and I/O modules that speak CC-Link IE TSN — which is exactly the network position both CVE-2026-13584 and CVE-2025-3511 assume an attacker already holds.
CVE-2026-13584: message tampering with no patch planned
Mitsubishi Electric's own PSIRT advisory (2026-005) describes an Improper Enforcement of Message Integrity During Transmission in a Communication Channel vulnerability (CWE-924): "an attacker with access to a CC-Link IE TSN network may be able to tamper with communication data by sending specially crafted packets under specific timing conditions," with the effect of a "denial-of-service (DoS) condition in the affected product by interfering with its control function or causing it to operate incorrectly." The CVSS v4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N, base score 7.1) marks it adjacent-network, low-complexity and requiring no privileges or user interaction — the attacker only needs a foothold on the CC-Link IE TSN segment itself.
The affected-products table in Mitsubishi's advisory spans 35 product categories, "all versions," including:
| Product category | Example models |
|---|---|
| MELSEC MX Controllers | MXR300-16/32/64, MXF100 series |
| Master/local communication modules | RJ71GN11-T2/SX/EIP, FX5-CCLGN-MS |
| Motion modules and control software | RD78G4/G8/G16/G64, SWM-G |
| AC servos | MELSERVO-J5, MELSERVO-JET |
| Industrial robot network cards | CR800-D series Network Base Card (2F-DQ535-TSN) |
| Inverters | FR-A800/F800/E800 series |
| HMIs | GOT3000 Series |
| SDKs and development kits | CC-Link IE TSN Master/Local module SDK, remote station software development kits |
Mitsubishi's advisory is explicit that no fix is planned. Its mitigations are entirely network- and physical-layer: restrict physical access to the affected products and their CC-Link IE TSN network segment (site access control, locked control panels, locked Ethernet ports with port-lock accessories); operate the products only inside a trusted network where a firewall blocks communication with untrusted networks and hosts; and correctly configure credentials and access privileges on boundary network devices.
Is this a one-off, or a pattern?
CVE-2026-13584 is not CC-Link IE TSN's first disclosed vulnerability. CVE-2025-3511, published 25 April 2025 under the same Mitsubishi Electric PSIRT process, is an Improper Validation of Specified Quantity in Input vulnerability (CWE-1284), CVSS v3.1 base score 7.5, vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H — fully remote, unauthenticated, no user interaction. NVD's record describes a remote attacker triggering denial-of-service by sending a specially crafted UDP packet to CC-Link IE TSN Remote I/O modules (the NZ2GN series), Analog/Digital Converter modules, FPGA modules, and a named set of MELSEC iQ-R and iQ-F series modules (RJ71GN11-T2, RJ71EN71, the R04/08/16/32/120ENCPU family, FX5-CCLGN-MS, FX5-ENET, FX5-ENET/IP) and CP610/CP620 communication LSIs.
Two independently disclosed, network-reachable denial-of-service findings against the same protocol family within roughly 15 months — both from Mitsubishi's own PSIRT, both republished by CISA, neither with a complete patch across the full affected fleet — is the kind of repeat pattern NIST SP 800-82's OT security guidance assumes will keep happening in legacy-influenced deterministic fieldbus protocols, and why compensating network controls, not a wait for a patch, are the realistic posture.
A workable starting point
Inventory every device that speaks CC-Link IE TSN before deciding anything elseBoth CVEs affect dozens of specific product/model combinations at "all versions" — you cannot assess exposure without knowing exactly which Mitsubishi Electric and CC-Link-compatible hardware is on the network and at what firmware revision. Segment the CC-Link IE TSN network behind an industrial DMZ, the same compensating control NIST SP 800-82 and the Purdue Model recommend for every unauthenticated or integrity-unprotected legacy OT protocol — do not assume TSN's real-time scheduling features imply any security boundary. Treat Mitsubishi's physical-access mitigations as the primary control, not a stopgap, since no firmware patch for CVE-2026-13584 exists: lock control panels, lock or restrict unused Ethernet ports with port-lock hardware, and manage physical site access to anywhere these products are installed. Re-check both advisories directly before actingMitsubishi's advisory for CVE-2026-13584 was already updated once (17 September 2026, revising the affected-products list); confirm you are reading the current version and the current CISA republication before planning remediation.
SoftWSP's OT Snapshot builds a passive, factual picture of which devices on a shop floor are actually speaking CC-Link IE TSN and to which other hosts, read from a mirror port without touching production traffic — a starting point for scoping exposure to CVE-2026-13584 and CVE-2025-3511 before deciding on segmentation or access changes: see OT Snapshot.
This guide summarizes CLPA's own public technology page, Mitsubishi Electric's own PSIRT advisory PDF (2026-005), and NVD's published CVE records for CVE-2026-13584 and CVE-2025-3511, each fetched directly for this guide on 5 November 2026. It is not a substitute for Mitsubishi Electric's current advisory, CISA's current ICSA-26-211-07 record, or an engineer's assessment of a specific deployment, and does not constitute security advice.
Sources
- CLPA (CC-Link Partner Association): CC-Link IE TSN technology overview (TSN architecture, IEEE 802.1AS/802.1Qbv, OSI Layer 2 placement)
- Mitsubishi Electric Corporation: Security Advisory 2026-005 — Information tampering and Denial-of-service (DoS) vulnerability in CC-Link IE TSN communication protocol (released 30 July 2026, updated 17 September 2026, PDF)
- NVD: CVE-2026-13584 — CVSS v4.0 7.1, CWE-924, CC-Link IE TSN communication protocol message-integrity vulnerability
- NVD: CVE-2025-3511 — CVSS v3.1 7.5, CWE-1284, CC-Link IE TSN Remote I/O and MELSEC iQ-R/iQ-F module UDP input-validation vulnerability
- CISA: ICS Advisory ICSA-26-211-07 — Mitsubishi Electric CC-Link IE TSN Communication Protocol (Update A)
Frequently asked questions
What is CC-Link IE TSN, and who maintains it?
CC-Link IE TSN is an open industrial Ethernet network maintained by the CC-Link Partner Association (CLPA), a Japan-based organization with, per its own site, more than 4,500 partner companies worldwide. CLPA's own technology page states it is "the world's first to adopt TSN (Time-Sensitive Networking) technology, which extends the standard Ethernet," placing the CC-Link IE TSN protocol at Layer 2 of the OSI reference model alongside standard Ethernet protocols running at Layers 3–7. For time synchronization, CLPA's page states the network uses IEEE 802.1AS to achieve "highly accurate time synchronization accuracy within ±1 μs," and IEEE 802.1Qbv to divide communication cycles into time slots so each connected station can schedule frame transmission according to priority. CC-Link IE TSN is the newest, "third generation" member of the broader CC-Link family, which also includes the original CC-Link fieldbus, CC-Link/LT for sensors and actuators, and CC-Link IE Field Network — the TSN variant is specifically positioned by CLPA for mixing different network traffic types on one physical network to support Industrial IoT (IIoT) and smart-factory deployments.
What does CVE-2026-13584 actually let an attacker do?
Per Mitsubishi Electric's own PSIRT advisory (2026-005, released 30 July 2026, last updated 17 September 2026), CVE-2026-13584 is an Improper Enforcement of Message Integrity During Transmission in a Communication Channel vulnerability (CWE-924) with a CVSS v4.0 base score of 7.1. Mitsubishi's advisory states plainly: "An attacker with access to a CC-Link IE TSN network may be able to tamper with communication data by sending specially crafted packets under specific timing conditions," and that "as a result, the attacker may be able to cause a denial-of-service (DoS) condition in the affected product by interfering with its control function or causing it to operate incorrectly." The advisory lists 35 distinct product categories as affected, spanning MELSEC MX Controllers, master/local communication modules, motion modules, AC servos (MELSERVO-J5 and -JET), industrial robot network cards, inverters, GOT3000 HMIs and multiple SDKs — all at "all versions," meaning no unaffected firmware revision exists. CISA republished the finding as ICSA-26-211-07 (Update A).
Is there a patch for CVE-2026-13584, and what does Mitsubishi recommend instead?
No. Mitsubishi Electric's own advisory states explicitly that no fix is planned, and directs customers to mitigations instead. The advisory's "Mitigations / Workarounds" section recommends, verbatim in substance: restrict physical access to the affected products and to the CC-Link IE TSN network segment they connect to — by controlling site access, locking control panels that house the affected products or network devices, and locking Ethernet ports with port-lock accessories; use the affected products only within a trusted network where communication with untrusted networks and hosts is blocked by a firewall or equivalent control; and appropriately configure credentials and access privileges on network devices sitting at the boundary between trusted and external networks. Mitsubishi credits the discovery to Alessandro Di Pinto, Giovanni Dini Gentilini, Luca Cremona and Gabriele Quagliarella of Nozomi Networks, Inc. Because the vulnerability sits in the protocol's own message-integrity design rather than in one product's implementation bug, a firmware patch for any single device would not close the underlying gap across the other 34 affected product lines — which is consistent with Mitsubishi choosing network-segmentation mitigations over a patch.
Is CVE-2026-13584 the first disclosed vulnerability in CC-Link IE TSN products?
No — it is at least the second within roughly 15 months. CVE-2025-3511, published 25 April 2025 (also credited to Mitsubishi Electric's own PSIRT disclosure), is an Improper Validation of Specified Quantity in Input vulnerability (CWE-1284) with a CVSS v3.1 base score of 7.5 (vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) — fully network-exploitable with no privileges or user interaction required. NVD's record describes it as allowing a remote, unauthenticated attacker to trigger denial-of-service by sending a specially crafted UDP packet to affected CC-Link IE TSN Remote I/O modules (NZ2GN series), Analog/Digital Converter modules, FPGA modules, several MELSEC iQ-R and iQ-F series modules (including RJ71GN11-T2, RJ71EN71, the R04/08/16/32/120ENCPU family, FX5-CCLGN-MS, FX5-ENET, FX5-ENET/IP), and CP610/CP620 communication LSIs. Two network-reachable denial-of-service findings against the same protocol family inside roughly 15 months is a pattern worth tracking, not a one-off.
In this cluster

Questions about this page?

