Root command execution by authenticated users
Published May 19, 2026 · Updated May 19, 2026
OS command injection in ScadaBR 1.2.0 allows remote authenticated users to execute arbitrary commands as root over the network. Public advisories do not disclose the affected endpoint, input, or command-building code. Low-privileged access is required by the CNA assessment; successful exploitation grants root-level control of the SCADA host.
Summary
What happened
OS command injection in ScadaBR 1.2.0 allows remote authenticated users to execute arbitrary commands as root over the network. Public advisories do not disclose the affected endpoint, input, or command-building code. Low-privileged access is required by the CNA assessment; successful exploitation grants root-level control of the SCADA host.
The record
- CVE
- CVE-2026-8603
- Published
- May 19, 2026
- Updated
- May 19, 2026
- Vendor
- ScadaBR
- Product
- ScadaBR
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 19, 2026CVE publishedPublication date reported by the CVE source.
- May 19, 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.2.0
What conditions does exploitation require?
What is affected?
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