Skip to main content
Mallory
HighVulnerability

CVE-2025-54850: DoS in Socomec DIRIS Digiware M-70 Modbus RTU over TCP configuration change sequence

Published Dec 1, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS0.34%28th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Socomec
IdentifiersCVE-2025-54850CWE-400

A denial-of-service vulnerability in Socomec DIRIS Digiware M-70 firmware 1.6.9 exists in the Modbus TCP / Modbus RTU over TCP handling logic. An unauthenticated remote attacker can send a specific sequence of Modbus RTU over TCP messages to TCP port 503 using function code 0x06 (Write Single Register) to force a configuration change that leaves the device in a persistent denial-of-service state. The documented trigger sequence writes: (1) register 58112 with value 1000 (indicating a configuration change will follow), (2) register 29440 with a value corresponding to the new Modbus address, and (3) register 57856 with value 161 to commit the configuration change. After the commit, the device enters a DoS condition.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation renders the DIRIS Digiware M-70 device inoperable (denial of service), disrupting Modbus communications and the gateway’s availability for power monitoring/energy management functions in affected environments.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to Modbus services (including Modbus RTU over TCP on TCP/503) to trusted hosts/segments only (e.g., ICS network segmentation/ACLs/firewalling). Deploy available IDS signatures (Snort rules referenced by Talos/Snort.org) to detect exploitation attempts targeting this issue.

Remediation

Patch, then assume compromise.

Upgrade Socomec DIRIS Digiware M-70 from firmware 1.6.9 to firmware 1.7 or later (vendor patches released).

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SocomecDiris M-70 Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2025-54850 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-54850 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-54850?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-54850.
Is there a patch for CVE-2025-54850?
Upgrade Socomec DIRIS Digiware M-70 from firmware 1.6.9 to firmware 1.7 or later (vendor patches released).
What products are affected by CVE-2025-54850?
Socomec Diris M-70 Firmware.
How severe is CVE-2025-54850?
CVE-2025-54850 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.34% (28th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.