CVE-2026-78319: TOCTOU Vulnerability in file exchange
A service running on the affected products contains a potential Time-of-Check Time-of-Use (TOCTOU) race condition.
An unauthenticated remote attacker could exploit this race condition to bypass intended security controls.
This may result in the execution of unauthorized code.
Security readout for executives and security teams
Plain-English summary
A flaw in the file-exchange service on specified Sauter building-automation products may let an unauthenticated remote attacker bypass security checks and run unauthorized code. Successful exploitation could compromise device confidentiality, integrity, and availability. The supplied sources do not identify a patch or confirm exploitation in the wild.
Executive priority
Prioritize immediate exposure assessment and containment. Network-accessible affected devices could permit full device compromise without credentials. Confirm the ambiguous version scope with Sauter, isolate exposed systems, and apply vendor guidance promptly. There is no supplied evidence of active exploitation, but the potential impact and attack prerequisites justify urgent action.
Technical view
CVE-2026-78319 is a CWE-367 time-of-check/time-of-use race condition. A remote, unauthenticated attacker may exploit a timing gap between file validation and use, potentially causing unauthorized code execution. It carries CVSS 4.0 score 9.3 with network reachability, low complexity, no privileges, and no user interaction.
Likely exposure
Potential exposure includes Sauter modu680-AS, modu660-AS, modu612-LC, ecos504, and ecos505 devices associated with version 1.0.0, particularly when their affected service is network-accessible. The bundle also reports a default status of unaffected, making the precise version scope ambiguous; confirm applicability through the vendor advisory and device inventory.
Exploitation context
The issue is remotely reachable, requires no authentication or user interaction, and is assessed as low complexity. However, the bundle reports no CISA KEV listing and provides no evidence of active exploitation, public exploit availability, or observed attacks. Treat exploit status as unconfirmed.
Researcher notes
The core condition is a TOCTOU race in a file-exchange service, mapped to CWE-367. The sources do not disclose the checked object, race window, affected endpoint, patch version, indicators of compromise, or reliable detection signature. Avoid assuming every listed version is vulnerable because the structured bundle simultaneously labels version 1.0.0 and states a default unaffected status.
Mitigation direction
Review the CERT@VDE and Sauter CSAF advisories for corrected firmware or vendor-prescribed mitigation.
Restrict access to affected device services to authorized management networks and systems.
Remove unnecessary internet exposure and segment building-automation devices from general corporate networks.
Escalate patch applicability questions to Sauter because the supplied version status is ambiguous.
Validation and detection
Inventory the five named Sauter product models and record their exact firmware versions.
Confirm whether each device exposes the affected file-exchange service to untrusted networks.
Compare product identifiers and firmware against the latest vendor CSAF advisory.
Review device and network logs for unexpected file exchanges, service changes, or code execution indicators.
After remediation, verify firmware versions, service reachability, and intended security controls.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-367: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-367 · source CWE mapping
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.