Unauthenticated code execution via firmware update race
Published Sep 1, 2026 · Updated Sep 1, 2026
TOCTOU in the firmware update service of SAUTER building controllers allows remote attackers to execute unauthorized code. The vendor identifies a race between checking and using an update resource but does not disclose the resource, operation, or request sequence that opens the race. No authentication or user interaction is required, and successful exploitation grants full control of the controller and its building-automation functions.
Summary
What happened
TOCTOU in the firmware update service of SAUTER building controllers allows remote attackers to execute unauthorized code. The vendor identifies a race between checking and using an update resource but does not disclose the resource, operation, or request sequence that opens the race. No authentication or user interaction is required, and successful exploitation grants full control of the controller and its building-automation functions.
The record
- CVE
- CVE-2026-78319
- Published
- Sep 1, 2026
- Updated
- Sep 1, 2026
- Vendor
- Fr. Sauter AG
- Product
- SAUTER modu680-AS
- Classifications
- CWE-367, CAPEC-29, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 2026CVE publishedPublication date reported by the CVE source.
- Sep 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <4.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo