Skip to main content
Mallory
← Back to News
industrial-control-system-vulnerabilitycritical-infrastructure-threatwidely-deployed-product-advisoryhealthcare-sector-threat

DoS Vulnerabilities in Socomec DIRIS M-70 IIoT Gateway Found via Single-Thread Emulation Fuzzing

Vulnerability Disclosure · 2 sources · Updated 5mo ago · First seen Feb 19, 2026

DoS Vulnerabilities in Socomec DIRIS M-70 IIoT Gateway Found via Single-Thread Emulation Fuzzing

Cisco Talos disclosed six denial-of-service vulnerabilities (six CVEs) affecting the Socomec DIRIS M-70 industrial gateway used for power monitoring and energy management, with impact concentrated in environments such as critical infrastructure, data centers, and healthcare. The issues affect firmware 1.6.9 and can be triggered remotely without authentication, potentially disrupting Modbus-related processing and causing operational outages or instability in deployments where the gateway is a key communications component (RS485/Ethernet; protocols including Modbus RTU/TCP, BACnet IP, and SNMP).

The research describes a technique to overcome hardware debugging constraints caused by the device’s STM32 Code Read-out Protection (RDP) Level 1, which blocks traditional JTAG-based inspection. Talos obtained an unencrypted firmware update and used a “good enough” emulation strategy: emulating only the single Modbus-handling thread (rather than full-system emulation) with Unicorn Engine, then applying coverage-guided fuzzing with AFL and using Qiling to visualize coverage and analyze crash root causes. Socomec reportedly patched the vulnerabilities following coordinated disclosure via Cisco’s policy.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Feb 18, 2026 – Feb 19, 2026
  1. Feb 19, 20269mo ago

    Snort detection coverage is published for exploitation attempts

    Detection content was made available in the form of Snort rules to help identify attempts to exploit the DIRIS M-70 vulnerabilities. This accompanied public reporting on the six Modbus-related DoS flaws.

  2. Feb 18, 20269mo ago

    Six CVEs are disclosed and Socomec releases firmware fixes

    The six vulnerabilities were disclosed under Cisco's coordinated disclosure process and assigned CVEs. Socomec released patches and advised customers to upgrade to firmware version 1.7 or later to remediate the issues.

  3. Feb 18, 20269mo ago

    Talos identifies six DoS vulnerabilities in Socomec DIRIS M-70 firmware 1.6.9

    The fuzzing campaign uncovered six denial-of-service flaws in Socomec DIRIS M-70 firmware version 1.6.9. The issues allow unauthenticated remote attackers to crash or render the device inoperable by sending crafted Modbus messages over the network.

  4. Feb 18, 20269mo ago

    Talos researcher develops single-thread emulation for DIRIS M-70 fuzzing

    While analyzing the Socomec DIRIS M-70 industrial gateway, a Cisco Talos researcher used an unencrypted firmware update and SRAM dumping to work around STM32 RDP Level 1 protections, then emulated only the Modbus-handling thread with Unicorn and AFL. The approach was later adapted to Qiling to improve debugging and code-coverage visualization during crash triage and root-cause analysis.

Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.