Skip to main content
Mallory
HighVulnerability

CVE-2025-54848: DoS in Socomec DIRIS Digiware M-70 1.6.9 Modbus TCP Write Single Register (FC=6) 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.45%40th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Socomec
IdentifiersCVE-2025-54848CWE-400

A denial-of-service vulnerability in Socomec DIRIS Digiware M-70 firmware 1.6.9 exists in the device’s Modbus TCP / Modbus RTU over TCP handling on TCP port 502. An unauthenticated attacker can send a specific sequence of Modbus TCP Write Single Register (function code 6) requests that triggers a configuration change workflow and leaves the device in a persistent denial-of-service state. The documented trigger sequence is: (1) write register 58112 with value 1000 to indicate a configuration change will follow; (2) write register 29440 with a value corresponding to the new Modbus address; (3) write register 57856 with value 161 to commit the configuration change. After this sequence, 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 operational role in power monitoring/energy management environments.

Mitigation

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

Restrict network access to Modbus services (TCP/502) to trusted hosts/segments (e.g., ICS VLAN/ACLs/firewalling) and monitor/detect exploitation attempts using available Snort rules from Snort.org targeting these Talos-reported Modbus DoS conditions.

Remediation

Patch, then assume compromise.

Upgrade Socomec DIRIS Digiware M-70 from firmware 1.6.9 to firmware 1.7 or later (vendor patches were released per the referenced Talos disclosure).

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 Digiware M-70 Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2025-54848 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-54848 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-54848?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-54848.
Is there a patch for CVE-2025-54848?
Upgrade Socomec DIRIS Digiware M-70 from firmware 1.6.9 to firmware 1.7 or later (vendor patches were released per the referenced Talos disclosure).
What products are affected by CVE-2025-54848?
Socomec Diris Digiware M-70 Firmware.
How severe is CVE-2025-54848?
CVE-2025-54848 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.45% (40th 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 signaturesYARA, 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.