CVE-2025-55221VulnerabilityPublished 1 Dec 2025

CVE-2025-55221: Socomec DIRIS Digiware M-70 · Missing Authentication

Affects Socomec DIRIS Digiware M-70Source CVE Database V5

Not known to be exploited · CVSS 8.6 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Socomec DIRIS Digiware M-70	Affected =1.6.9	Fixed in–

AI-suggested

1. Network Segmentation: Isolate the Socomec DIRIS Digiware M-70 devices within dedicated network segments that restrict access to trusted management systems only. 2. Firewall Rules: Implement strict firewall policies to block or filter Modbus TCP traffic (port 502) from untrusted or external networks, allowing only authorized IP addresses to communicate with the devices. 3. Intrusion Detection/Prevention: Deploy network monitoring tools capable of detecting anomalous Modbus TCP packets and potential exploitation attempts targeting port 502. 4. Vendor Coordination: Engage with Socomec for official patches or firmware updates addressing CVE-2025-55221 and apply them promptly once available. 5. Access Controls: Enforce strong access control policies on management interfaces and restrict physical and network access to the devices. 6. Incident Response Planning: Prepare response procedures for potential denial of service incidents affecting power monitoring systems to minimize downtime. 7. Regular Audits: Conduct periodic security assessments of OT networks to identify unauthorized access or suspicious activity related to Modbus communications. These measures go beyond generic advice by focusing on network-level controls and operational readiness specific to the affected product and protocol.

Description

A denial of service vulnerability exists in the Modbus TCP and Modbus RTU over TCP USB Function functionality of Socomec DIRIS Digiware M-70 1.6.9. A specially crafted network packet can lead to a denial of service. An attacker can send an unauthenticated packet to trigger this vulnerability.This vulnerability is specific to the malicious message sent via Modbus TCP over port 502.

Impact

For European organizations, this vulnerability poses a significant risk to the availability of power monitoring and management systems that rely on the Socomec DIRIS Digiware M-70. Disruption of these devices could lead to loss of real-time power data, impairing operational decision-making and potentially causing cascading failures in industrial processes or critical infrastructure such as energy grids, manufacturing plants, and data centers. The lack of authentication means attackers can exploit the vulnerability remotely without credentials, increasing the attack surface. This could facilitate denial of service attacks from external threat actors or insiders with network access. The impact is particularly severe for sectors where continuous power monitoring is essential for safety and regulatory compliance. Additionally, the scope change in the CVSS score indicates that the vulnerability could affect other components or systems relying on the device's availability, amplifying the operational impact. European organizations with interconnected industrial control systems (ICS) and operational technology (OT) environments must consider this vulnerability a high priority to avoid service interruptions and potential safety hazards.

CWE-306Missing Authentication for Critical Function (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #21OWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Architecture and Design
Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
V1.2.4 (opens in a new tab)
Attack patterns
Choosing Message Identifier (opens in a new tab)
Force the System to Reset Values (opens in a new tab)
Using Unpublished Interfaces or Functionality (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
Communication Channel Manipulation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

talosintelligence.com/vulnerability_reports/TALOS-2025-2251 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Dec 2025, 17:07 UTC

WeaknessesCWE-306

Technical details

References

Community reviews

Related threats