As reported by CISA in advisory ICSA-26-293-04, Hitachi Energy has confirmed multiple vulnerabilities affecting its MicroSCADA X SYS600 product — a supervisory control and data acquisition system deployed across energy-sector critical infrastructure worldwide. The advisory details three CVEs that, while individually rated medium-to-high, collectively create a meaningful attack surface for any adversary with foothold access to an operational technology (OT) network.

Security Impact: As reported by CISA in advisory ICSA-26-293-04, Hitachi Energy has confirmed multiple vulnerabilities affecting its MicroSCADA X SYS600 product — a supervisory control and data acquisition system deployed across energy-sector critical infrastructure worldwide.

Vulnerability Summary

CVECVSS v3.1SeverityDescriptionAffected Versions
CVE-2026-98525.0MediumCSV injection via malicious formula in log export — allows data exfiltration and potential code execution depending on user environmentSYS600 ≤10.7
CVE-2026-98537.8HighAuthentication bypass — any OS-authenticated user can read and modify SYS600 application objects without SYS600-level authenticationSYS600 ≤10.7
CVE-2026-9854Not fully detailedPendingAdditional vulnerability referenced in advisory; details may be available in vendor advisorySYS600 ≤10.7

Why This Matters

The most concerning issue is CVE-2026-9853 — a fundamental breakdown in the trust boundary between the host operating system and the SYS600 application layer. When any OS-level user can interact with application objects without SYS600 authentication, the SCADA system's access control model is effectively circumvented. In energy-sector environments where SCADA systems manage grid operations, substation automation, or pipeline controls, this isn't a minor inconvenience — it's a potential pathway to unauthorized configuration changes, data tampering, or operational disruption.

CVE-2026-9852, while rated medium, deserves more attention than its score suggests. CSV injection via log exports is a well-understood attack vector, but in OT environments it becomes particularly dangerous. If an attacker can inject malicious formulas into SCADA log messages — achievable through SCIL scripts, log injection, or the SYS600 broker — and an operator later exports those logs to a spreadsheet, the attacker has effectively bridged the air gap between the OT system and the analyst's workstation. This is a classic pivot technique.

Who Is Most At Risk

Why This Matters
Energy utilities — the primary deployment sector, with systems installed worldwide
Systems still running SYS600 ≤10.7 — no patch applied, fully exposed
Mixed-trust environments — where OS-level users and SYS600 application users are not strictly separated
Operations teams that regularly export logs to Excel — the CSV injection vector is only as dangerous as the spreadsheet consumption habit
The interplay between CVE-2026-9853 and CVE-2026-9852 is the real story here. An OS-level user exploiting the auth bypass could inject malicious log entries, which then propagate through CSV exports to compromise analyst workstations. This is a chained attack path, not three independent bugs.

Shield53 Recommendations

Immediate Actions

  • Patch to version 10.8 — Hitachi Energy has released this as the remediation version. Verify whether 10.8 addresses all three CVEs or only a subset, and confirm with the vendor advisory directly.
  • Restrict OS-level access — Until patching is complete, minimize the number of OS-level accounts on SYS600 hosts. Apply least-privilege principles and audit existing local accounts.
  • Disable or sandbox log exports — If operators must export logs, use a hardened environment with macro execution disabled. Consider DLP controls on CSV files originating from SYS600.
  • Monitor for anomalous SCIL script execution — Since CVE-2026-9852 can be triggered via SCIL scripts, instrument logging around script execution and flag unexpected or unauthorized scripts.
  • Segment SYS600 hosts — Ensure SYS600 servers are not reachable from general IT networks. Validate firewall rules and jump-host configurations.

Longer-Term Hardening

  • Implement application-layer authentication auditing to detect CVE-2026-9853-style bypass attempts
  • Adopt a formal change management process for SCIL scripts and log configurations
  • Review Hitachi Energy's security hardening guides for SYS600 and align with IEC 62443 zoning practices
  • Establish a quarterly vulnerability scan cadence for all OT assets, not just IT-adjacent systems

These vulnerabilities are a reminder that SCADA systems are not just targets for nation-state actors — they're also vulnerable to the same class of design flaws we see in enterprise software. The energy sector's slow patch cycles amplify the risk. Treat this advisory as urgent, not routine.