Back to Intelligence

CVE-2026-13584: Mitsubishi Electric MELSEC MX-R Controller DoS Vulnerability — Detection & Mitigation

SA
Security Arsenal Team
August 1, 2026
6 min read

CISA has released ICS Advisory ICSA-26-211-07 regarding a critical security issue affecting the Mitsubishi Electric CC-Link IE TSN Communication Protocol. Tracked as CVE-2026-13584, this vulnerability poses a severe risk to operational continuity in industrial environments.

For defenders, the immediate concern is the low barrier to exploitation: an attacker requires only access to the same network segment. This specific condition bypasses traditional perimeter defenses, rendering deep packet inspection (DPI) at the boundary insufficient. If your operational technology (OT) network relies on Mitsubishi MELSEC MX Controller MX-R series, you are currently in a high-risk state for data tampering and Denial-of-Service (DoS). Immediate segmentation and patch management are non-negotiable.

Technical Analysis

Affected Products:

  • Mitsubishi Electric MELSEC MX Controller MX-R Model MXR300-16 (All versions)
  • Mitsubishi Electric MELSEC MX Controller MX-R Model MXR300-32 (All versions)
  • Mitsubishi Electric MELSEC MX Controller MX-R Model MXR300-64 (All versions)

Vulnerability Details:

  • CVE ID: CVE-2026-13584
  • Impact: Denial of Service (DoS), Data Tampering, Loss of Control
  • Vector: Network Adjacent (Layer 2)

Mechanism of Exploitation: The vulnerability stems from improper validation of input within the CC-Link IE TSN communication protocol implementation. An attacker situated on the same Layer 2 network segment can transmit specially crafted packets. Crucially, the exploit requires specific timing conditions to interfere with the controller's cycle time. If successful, the attacker can overwrite legitimate communication data or inject malformed frames, causing the MELSEC controller to enter a fault state, halt operations, or execute control logic incorrectly.

Exploitation Status: While CISA has not confirmed active exploitation in the wild at the time of this advisory, the specificity of the "timing conditions" suggests a sophisticated understanding of the protocol, often indicative of advanced research or potential weaponization in nation-state toolkits targeting industrial control systems (ICS). We treat this as a high-severity, actionable threat.

Detection & Response

SIGMA Rules

The following Sigma rules focus on identifying anomalous Layer 2 traffic targeting Mitsubishi Electric MAC OUIs and potential indicators of protocol manipulation leading to a DoS.

YAML
---
title: Potential CC-Link IE TSN Injection - Anomalous Traffic to Mitsubishi OUI
id: a1b2c3d4-5678-90ab-cdef-1234567890ab
status: experimental
description: Detects potential packet injection attempts targeting Mitsubishi Electric controllers by monitoring for high-frequency or irregular traffic to specific MAC OUIs (Mitsubishi: 00:00:0E, 00:E0:3C, 00:90:4C).
references:
  - https://www.cisa.gov/news-events/ics-advisories/icsa-26-211-07
author: Security Arsenal
date: 2026/04/18
tags:
  - attack.impact
  - attack.t0815
logsource:
  category: network
  product: zeek
  definition: 'fields: https://github.com/Corelight/zeek-specs/blob/master/scripts/base/protocols/conn/main.zeek'
detection:
  selection_mac:
    dst_mac|startswith:
      - '00:00:0E'
      - '00:E0:3C'
      - '00:90:4C'
  selection_anomaly:
    duration|lt: 0.1
    orig_bytes|gt: 100
  condition: selection_mac and selection_anomaly
falsepositives:
  - High-speed normal I/O polling during peak operations
level: high
---
title: Industrial Controller DoS - Sudden Drop in Heartbeat/Integrity Traffic
id: b2c3d4e5-6789-01bc-def2-234567890bcd
status: experimental
description: Detects signs of a Denial-of-Service on Mitsubishi controllers by identifying a sudden cessation of expected protocol traffic (CC-Link IE TSN) followed by a flood of reset packets.
references:
  - https://www.cisa.gov/news-events/ics-advisories/icsa-26-211-07
author: Security Arsenal
date: 2026/04/18
tags:
  - attack.impact
  - attack.t0814
logsource:
  category: network
  product: any
detection:
  selection_flood:
    protocol|contains: 'TCP'
    destination_port|startswith: '9600' # Common CC-Link port range if encapsulated, adjust per environment
    event_type: 'flow'
  filter_heartbeat:
    connection_state|contains: 'EST'
  timeframe: 30s
  condition: selection_flood and not filter_heartbeat | count() > 100
falsepositives:
  - Network reconfiguration or rapid scanning of the OT network
level: critical

KQL (Microsoft Sentinel / Defender)

Use this query to hunt for sudden spikes in traffic volume towards your known OT asset ranges or specific MAC address prefixes associated with Mitsubishi Electric.

KQL — Microsoft Sentinel / Defender
let MitsubishiOUIs = dynamic(["00:00:0E", "00:E0:3C", "00:90:4C"]);
DeviceNetworkEvents
| where Timestamp > ago(1h)
| where DeviceCustomHexString3 in (MitsubishiOUIs) // Assuming DeviceCustomHexString3 maps to Destination MAC in your CEF config
| summarize TotalBytes = sum(SentBytes + ReceivedBytes), PacketCount = count() by DeviceName, SourceIP, bin(Timestamp, 5m)
| where PacketCount > 1000 // Threshold tuning required based on baseline I/O cycle
| project TimeGenerated, DeviceName, SourceIP, PacketCount, TotalBytes
| sort by PacketCount desc

Velociraptor VQL

This VQL artifact hunts for active network connections on engineering workstations or jump servers that communicate with known MAC OUIs of the vulnerable controllers, helping identify the source of potential "same segment" attacks.

VQL — Velociraptor
-- Hunt for connections to Mitsubishi Electric MAC OUIs
SELECT
  F.Address AS RemoteAddress,
  F.Port AS RemotePort,
  P.Name AS ProcessName,
  P.Pid,
  P.Cmdline,
  F.State
FROM foreach(row={
    SELECT Pid FROM pslist()
  }, query={
    SELECT
      F.Address,
      F.Port,
      F.State,
      P.Name,
      P.Pid,
      P.Cmdline
    FROM netstat(pid=Pid) AS F
    JOIN pslist() AS P
    ON P.Pid = F.Pid
    WHERE F.State = 'ESTABLISHED'
      AND regex_search(source=parse_string_with_regex(F.Address, '(.{2}):(.{2}):(.{2}):').submatches[0], pattern='^(00:00:0E|00:E0:3C|00:90:4C)$')
      // Note: MAC retrieval in netstat varies by OS; adjust column mapping for Windows/Linux ARP tables if direct mapping not available
})

Remediation Script (Bash)

Disclaimer: This script is intended for the firewall or gateway server protecting the OT segment. It enforces network segmentation by restricting access to the controller subnet.

Bash / Shell
#!/bin/bash
# Remediation: Enforce Network Segmentation for Mitsubishi MELSEC Controllers
# Usage: sudo ./harden_mitsubishi_segment.sh <controller_subnet>

CONTROLLER_SUBNET=$1
IPTABLES=/sbin/iptables

if [ -z "$CONTROLLER_SUBNET" ]; then
  echo "Usage: $0 <controller_subnet> (e.g., 192.168.10.0/24)"
  exit 1
fi

echo "[*] Applying strict access control for $CONTROLLER_SUBNET..."

# Flush existing rules on the CHAIN (or create a new chain)
$IPTABLES -N MITSUBISHI_CONTROL 2>/dev/null || $IPTABLES -F MITSUBISHI_CONTROL

# Allow traffic from known Engineering Workstations (Replace with actual IP(s))
# Example: Allow only from 10.0.0.50
ENGINEERING_STATION="10.0.0.50"
$IPTABLES -A MITSUBISHI_CONTROL -s $ENGINEERING_STATION -d $CONTROLLER_SUBNET -j ACCEPT

# Allow established/related connections
$IPTABLES -A MITSUBISHI_CONTROL -m state --state ESTABLISHED,RELATED -j ACCEPT

# Explicit DROP for all other traffic to controller subnet (Mitigates CVE-2026-13584)
$IPTABLES -A MITSUBISHI_CONTROL -d $CONTROLLER_SUBNET -j DROP

# Append to FORWARD chain (assuming this gateway routes to OT)
# Check if rule exists to prevent duplicates
if ! $IPTABLES -C FORWARD -j MITSUBISHI_CONTROL 2>/dev/null; then
  $IPTABLES -A FORWARD -j MITSUBISHI_CONTROL
  echo "[+] Rules applied successfully. Access restricted to $ENGINEERING_STATION."
else
  echo "[!] Rules already active."
fi

Remediation

  1. Network Segmentation (Immediate): The primary vector for CVE-2026-13584 is network adjacency. You MUST isolate the MELSEC MX-R controllers into a dedicated VLAN. Implement Access Control Lists (ACLs) on managed switches to strictly limit traffic to only authorized Engineering Workstations and HMI/SCADA servers. Block all other unsolicited Layer 2 and Layer 3 traffic to the controller subnet.

  2. Apply Firmware Updates: Mitsubishi Electric is expected to release updates shortly. Monitor the Mitsubishi Electric Security Advisory page (linked below) and your local distributor for patches specifically addressing CVE-2026-13584. Upon release, follow a rigorous testing methodology in a non-production environment before deploying to active control systems.

  3. Intrusion Detection Systems (IDS): Deploy industrial IDS (e.g., Nozomi, Dragos, Claroty) rules for CC-Link IE TSN protocol anomalies. Enable alerts for malformed frames and timing irregularities indicative of this exploit.

  4. Review CISA Recommendations: Review CISA Advisory ICSA-26-211-07 for specific mitigations. CISA recommends minimizing network exposure for all control system devices and ensuring they are not accessible from the internet.

Vendor Advisory: Mitsubishi Electric Security Advisory

Related Resources

Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.