Skip to main content
Mallory
HighVulnerability

CVE-2025-55222: DoS in Socomec DIRIS Digiware M-70 Modbus RTU over TCP USB Function (port 503)

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-55222CWE-306 · Missing Authentication for…

Information currently not available to provide a detailed, function-level vulnerability description beyond what is stated in the provided content. Based on the provided content: Socomec DIRIS Digiware M-70 firmware 1.6.9 contains a denial-of-service condition in its Modbus TCP / Modbus RTU over TCP “USB Function” handling. An unauthenticated attacker can send a specially crafted Modbus RTU over TCP message to TCP port 503 to trigger a device crash/unavailability. The content also characterizes the issue as missing authentication for a critical function (CWE-306).

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.

A remote, unauthenticated attacker can cause denial of service, rendering the DIRIS Digiware M-70 device unavailable/inoperable by sending a crafted Modbus RTU over TCP packet to port 503.

Mitigation

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

Restrict/segment network access to Modbus RTU over TCP service on TCP port 503 (e.g., ACLs/firewalling/VPN-only access) and monitor/detect suspicious Modbus traffic (the content notes Snort rules are available).

Remediation

Patch, then assume compromise.

Upgrade Socomec DIRIS Digiware M-70 from firmware 1.6.9 to firmware 1.7 or later (vendor patch level) as indicated in the provided content.

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-55222 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-55222 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-55222?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-55222.
Is there a patch for CVE-2025-55222?
Upgrade Socomec DIRIS Digiware M-70 from firmware 1.6.9 to firmware 1.7 or later (vendor patch level) as indicated in the provided content.
What products are affected by CVE-2025-55222?
Socomec Diris M-70 Firmware.
How severe is CVE-2025-55222?
CVE-2025-55222 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.