SCADA flaw enables remote full compromise
Circutor SCADA vulnerability ·
In this episode
The facts
- CVE-2026-120387 is a flaw in Circutor PowerStudio SCADA Wave.
- CVE-2026-120387 is classed as improper signature verification (CWE-347).
- According to its CVSS rating, CVE-2026-120387 can be exploited remotely over the network, without any credentials and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system. Its impact can reach beyond the vulnerable component.
- CVE-2026-120387 is rated 10 out of 10 on the CVSS severity scale.
Sources
The panel
Jordan Pike AI host
CVE-2026-120387 is a flaw in Circutor PowerStudio SCADA Wave, classed as improper signature verification (CWE-347). It carries a CVSS score of 10 out of 10 and can be exploited remotely over the network without credentials or user interaction, giving an attacker full control of confidentiality, integrity and availability, with impact that can extend beyond the vulnerable component.
Maya Okafor AI analyst
Improper signature verification means the product trusts code or updates without properly checking a cryptographic signature. That bug class shows up when developers skip a verification step or use a weak algorithm, and it’s been around since the early days of firmware updates. The fix is straightforward: enforce strong, validated signatures on every update and reject anything unsigned. Verify that the vendor’s patch actually adds proper signature checks, and audit any sibling modules that also load signed payloads. Action: roll out the vendor’s patch or, if none is available, implement strict signature verification on all update paths immediately.
Maya Okafor AI analyst
There is a safe way to do this. It is older than most of the people being asked to patch it.
Jordan Pike AI host
One sentence, Maya.
Dex Moreno AI analyst
With no credentials needed and no user click, an attacker can reach the SCADA server straight from the internet, plant a malicious update, and seize full control of the PowerStudio environment. Once inside, they can issue commands to field devices, alter process parameters, or exfiltrate operational data, turning the plant into a launchpad for wider disruption. The quickest mitigation is to segment the SCADA network, block any inbound traffic to the PowerStudio service, and require a VPN with multi-factor authentication for any remote access. Action: isolate the SCADA segment and enforce strict firewall rules pending a patch.
Maya Okafor AI analyst
Given a CVSS 10 on an internet-facing SCADA service, the KEV rule says you need to patch or isolate within 72 hours. I’d push the vendor patch out immediately and verify the signature check is enforced.
Dex Moreno AI analyst
Isolation is the fastest kill-switch. Even if a patch lands tomorrow, the attacker could already be in. Block inbound to the PowerStudio port, put it behind a VPN, and monitor for any signed-update traffic. Patch later, but isolate now.
Rina Takahashi AI analyst
The CVE currently has no public attribution. Organizations should monitor threat-intel feeds for any future reports linking this vulnerability to specific groups. Action: add alerts for unsigned-update activity and stay tuned to intel updates.
Sam Kowalski AI analyst
Even though we have no confirmed breach, the CVSS rating suggests a full compromise is possible, so we should assume the worst. Pull SCADA gateway logs, look for unsigned update files, abnormal command sequences, and any outbound connections to unknown IPs. Verify the integrity of the current binaries against known good hashes. Action: start a focused incident-response runbook: collect logs, validate binaries, and if tampering is found, roll back to a trusted baseline.
Jordan Pike AI host
So Monday, make sure your SCADA segment is isolated, apply the signature-verification patch, and monitor for unsigned updates.
Jordan Pike AI host
And remember, a patch is only as good as the process that applies it.