dbcve.org
Diris M 70 FirmwareOperating system · Socomec

CVE-2025-26858

HIGH · 7.5 CVSS v3.1 Published 2025-12-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A buffer overflow vulnerability exists in the Modbus TCP functionality of Socomec DIRIS Digiware M-70 1.6.9. A specially crafted set of network packets can lead to denial of service. An attacker can send a sequence of unauthenticated packets to trigger this vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A buffer overflow vulnerability exists in the Modbus TCP implementation of the Socomec DIRIS Digiware M-70 power monitoring device version 1.6.9. An unauthenticated attacker can send specially crafted Modbus TCP packets that overflow a memory buffer, causing denial of service.

MitigationApply vendor firmware patch when available; meanwhile, isolate the device behind a firewall or VPN, disable unused Modbus TCP access, and monitor for anomalous network traffic to the device.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Diris M 70 FirmwareOperating system
Affected:= 1.6.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model
    Access the device management interface (web UI or console) and identify the exact device model. Verify it is a Socomec DIRIS Digiware M-70.
    Affected if The device is NOT a Socomec DIRIS Digiware M-70 (different models are not affected by this specific CVE).
  2. Check firmware version
    In the device web interface or management console, locate the firmware version information. This is typically found under System Info, Device Status, or About sections.
    Affected if The firmware version is exactly 1.6.9 (this is the only version listed as affected).
  3. Verify Modbus TCP is enabled
    Access the device configuration settings and check whether the Modbus TCP protocol is enabled. Look for settings related to Modbus communication, serial/TCP configuration, or communication protocols.
    Affected if Modbus TCP is disabled - the vulnerability cannot be exploited if the protocol is not enabled.
  4. Check network exposure of Modbus TCP port
    Scan the network or review firewall rules to determine if the device Modbus TCP port (default 502) is accessible from untrusted networks. Determine if the device is directly exposed to the internet or accessible from the corporate network.
    Affected if The device Modbus TCP port is accessible from untrusted networks (internet or guest VLANs), increasing exploit likelihood.
  5. Monitor for device crashes or unusual behavior
    Review device logs, network monitoring tools, or syslog entries for the device. Look for unexpected reboots, Modbus service failures, or abnormal error messages.
    Affected if The device exhibits frequent crashes, unexpected reboots, or Modbus service errors that coincide with external Modbus TCP traffic.

You are affected if you have a Socomec DIRIS Digiware M-70 running firmware version 1.6.9 with Modbus TCP enabled and accessible from a network where an unauthenticated attacker could send packets to the device.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch when available; meanwhile, isolate the device behind a firewall or VPN, disable unused Modbus TCP access, and monitor for anomalous network traffic to the device.

Fix this in Diris M 70 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26858 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26858 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data