Sauter modulo CVE-2026-78319

Exploitation requires network reachability to the vulnerable service running on a Sauter modu680-AS, modu660-AS, modu612-LC, ecos504 or ecos505 controller; no credentials and no user interaction are needed (PR:N/UI:N). The defining prerequisite is the TOCTOU timing window: the attacker must interleave a state change between the service's security check and its use, so successful exploitation depends on repeatedly racing that window rather than a single deterministic request - this limits reliability even though authentication is not required. Practical exposure is further limited by whether the controller's management service is reachable from the attacker's position; these OT devices are frequently deployed behind facility firewalls or on segmented BAS networks, which constrains who can attempt the race.

The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N with VC:H/VI:H/VA:H) describes an unauthenticated, network-reachable flaw with total system impact, which is why it scores 9.3. However, the vulnerability class is a race condition, so real-world exploitation requires reliably winning a timing window against the target service - a practical constraint the AT:N/AC:L metrics arguably understate; a more honest assessment carries an attack requirement (AT:P / AC:H). No EPSS score, KEV entry, or public POC was provided, so there is no evidence of active or automatable exploitation today; the priority rests on the criticality of the impact and the exposure of ICS/BAS devices rather than on demonstrated in-the-wild use. These are operational-technology controllers where patching cycles are slow and network exposure is often higher than it should be, so despite the absence of a known exploit this warrants prompt remediation. Conflict to verify: the CVSS models a trivial race (AT:N) while CWE-367 implies a timing-dependent condition - confirm exploitation feasibility with the vendor advisory.

An attacker who can reach a Sauter modulo/ecoS controller's network service - for example an internet-exposed or flat-OT-network device - rapidly and repeatedly triggers the vulnerable operation to hit the narrow window between the security check and the privileged use. On a successful race they bypass the authentication/authorization control and push unauthorized code onto the controller, gaining control over the building-automation logic. No public POC is known at time of analysis, and success depends on reliably winning the timing window.