VulnerabilityPublished 22 Oct 2025

CVE-2025-41724: Sauter modulo 6 devices modu680-AS · Failure to Handle Incomplete Element

Affects Sauter modulo 6 devices modu680-ASSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% 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:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
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: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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 22 Oct 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 26 Oct 2026.

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 or the CVSS exploit maturity 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
Sauter modulo 6 devices modu680-AS	Affected =0.0.0	Fixed in–

AI-suggested

Immediately implement network segmentation and access controls to restrict access to the wscserver interface on modulo 6 devices, limiting exposure to trusted management networks only.
Deploy firewall rules or intrusion prevention systems to detect and block malformed or incomplete SOAP requests targeting these devices.
Monitor device logs and network traffic for abnormal SOAP request patterns indicative of exploitation attempts.
Establish operational procedures for rapid manual reboot of affected devices upon detection of service crashes to minimize downtime.
Engage with Sauter or authorized vendors to obtain patches or firmware updates as soon as they become available.
Consider deploying redundant devices or failover mechanisms to maintain service continuity during potential outages.
Conduct regular security assessments and penetration tests focusing on industrial control system protocols and interfaces.
Educate operational technology (OT) staff about this vulnerability and the importance of monitoring and incident response readiness.
Where possible, disable or restrict SOAP services if not required for device operation.
Maintain an inventory of all affected devices and their network exposure to prioritize remediation efforts.

Description

An unauthenticated remote attacker can crash the wscserver by sending incomplete SOAP requests. The wscserver process will not be restarted by a watchdog and a device reboot is necessary to make it work again.

Impact

For European organizations, the primary impact of CVE-2025-41724 is a denial of service condition on Sauter modulo 6 devices modu680-AS, which are often used in building automation, HVAC control, and industrial environments. The inability of the wscserver to recover automatically after a crash means that affected devices will remain non-functional until manually rebooted, potentially causing prolonged downtime. This can disrupt critical infrastructure operations, reduce operational efficiency, and increase maintenance costs. Since the attack requires no authentication and can be launched remotely over the network, exposed devices are at significant risk. Confidentiality and integrity are not impacted, but availability degradation can affect safety systems, energy management, and facility operations. European organizations with large deployments of Sauter automation systems, especially in sectors like manufacturing, utilities, and commercial real estate, may face operational and financial consequences. The lack of a patch and the necessity for manual intervention increase the risk window. Additionally, regulatory compliance related to operational continuity and safety may be challenged if devices remain vulnerable and unpatched.

References

sauter.csaf-tp.certvde.com/.well-known/csaf/white/2025/vde-2025-060.json (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2025, 08:03 UTC

WeaknessesCWE-239

Technical details

References

Community reviews

Related threats