Skip to content
Security

Circutor PowerStudio SCADA Wave, CVE-2026-120387: a new CVE scored 10

·8 min read

The bottom line

If you run PowerStudio SCADA WAVE desktop at 24.8.0 or later but before 24.11.17.0, update to 24.11.17.0 or later this week. Start by finding the installed version. If you do not run this product, you can stop here.
Cover page of Circutor PowerStudio SCADA Wave, CVE-2026-120387: a new CVE scored 10Free analysis report · 10 pagesCircutor PowerStudio SCADA Wave, CVE-2026-120387: a new CVE scored 10The same note as a document you can keep or forward: what the sources say, who is affected, and what to do first.Download the analysis report →

At a glance

FactDetail
ProductCircutor PowerStudio SCADA Wave (CVE-2026-120387)
SeverityCritical: 10 (CVSS 4.0)
StatusA new CVE record, published by Circutor on 17 November 2026. Not on CISA's list of exploited vulnerabilities when we read it on 17 November 2026, which means nothing public says yet that anyone is using it.
Fixed in24.11.17.0 or later (the vendor's remediation text in the record; no date given)
Who looks firstAnyone running the PowerStudio SCADA WAVE desktop version, and the IT provider or integrator who installed it. The record lists no other Circutor product.

Does this apply to you?

Answer in order. Stop at the first no.
QuestionIf noIf yes
Do you run CIRCUTOR PowerStudio SCADA WAVE, desktop version?Nothing to do for this CVE.Check the version (next question).
Is the version 24.8.0 or later but before 24.11.17.0?Not in the record's range. 24.11.17.0 or later is the fixed release.You are in range. Go to the next question.
Can anyone untrusted reach the application over a network?Lower urgency, but still update at the next patch cycle.Reduce exposure now and update to 24.11.17.0 or later.

What it is

An attacker on the network, with no account, can send a login token that has no signature (algorithm set to “none”). The software accepts it. The attacker then acts as another user and reaches that user's functions.

Why it matters

Our reading is that a forged token skips the login altogether, so strong passwords and lockout rules do not help. The record scores it 10 on CVSS 4.0 and names the weakness as CWE-347. The attacker gets the rights of whichever user they pick, so an administrator account would give the most. The record does not say which functions are exposed.

What the vendor's advisory says

We read two pages on circutor.com and github.com. In short:

  • The vendor's cybersecurity page we read is general. It describes a disclosure process and a table of resolved cases, but gives no detail for this CVE.
  • A public repository of AI-found flaw disclosures was also among the sources. Its text does not name this CVE, so we do not treat it as evidence about this flaw.

Exposure by situation

These priorities are our judgement from what the sources say about who can use the flaw and how. They are not vendor ratings.

Where you stand, and how soon
Your situationPriorityTimeframe
An affected version that can be reached from the internetHighImmediately; restrict access, then update
An affected version reachable only from an internal networkMediumThis week
Version 24.11.17.0 or laterNoneNone for this CVE
A version below 24.8.0LowAsk the vendor; the record does not list it
The product is not run at allNoneNone for this CVE

Things people will get wrong

  • “It is only a desktop version, so nobody can reach it.” The record describes an unauthenticated remote attacker. It does not say the desktop version is shielded from the network.
  • “We have strong passwords, so we are covered.” The flaw accepts a token with no signature, so the attacker never needs a password.
  • “Any newer version is fixed.” The record names 24.11.17.0 as the first unaffected release. Check you are at that version or later.

The wording includes conditions the score may not show: needs privileges. Read the record before you decide it does not apply to you.

How we would triage it

This is our judgement.

Step 1: Find the versions you run

  • Ask who installed PowerStudio SCADA WAVE and on which machines. The record covers the desktop version.
  • Read the installed version and compare it with the range 24.8.0 up to, but not including, 24.11.17.0.

Step 2: Reduce exposure

  • Remove any route from the internet to the application until it is updated, because the attack needs no account.
  • Allow access only from the machines and people who need it.

Step 3: Update

  • Update to 24.11.17.0 or later, as the vendor's remediation text in the record says.
  • Do not rely on a changelog or forum post for this flaw; the sources we read name no other fix.

Step 4: Confirm the fix

  • Read the version again after the update and keep a record of it.
  • Ask your provider for written confirmation of the version on every machine.

To close it, read the version from the product itself, not from an old inventory, and save the output with the date. If you cannot update today, write down who owns it, the new date, and what limits exposure until then.

Send this to your IT provider

Copy it, change the names and dates, and send it. It is a draft for you to check, not a template tested with any provider.

Hello, we need to check CVE-2026-120387 in CIRCUTOR PowerStudio SCADA WAVE (desktop version). Please tell us whether we run it, on which machines, and which version. The affected range is 24.8.0 up to, but not including, 24.11.17.0. The fixed version is 24.11.17.0 or later. Please also tell us whether any installation can be reached from the internet. Could you confirm in writing the installed version and that the update is done, by [date]? Thank you.

The weakness behind it

The record classes this as CWE-347.

Likely ATT&CK mapping

MITRE ATT&CK is a public catalogue of the steps attackers take, from getting in to causing damage. No source has mapped this flaw to it yet, so the steps below are our prediction from what the record says the flaw allows. They are not MITRE's, the vendor's or CISA's, and an attacker may do other things.

Steps an attacker would likely take with this flaw
The step, in plain wordsStage of an attackWhy we think so
Exploit Public-Facing Application (T1190): Breaking in through a service that faces the internet, such as a web server, VPN or login page.Initial Access: getting inThe record describes an unauthenticated remote attacker, so the flaw would likely be reached over a network and used to get into the application.
Use Alternate Authentication Material (T1550): Using a stolen token or hash instead of a password to log in.Defense Evasion: avoiding detectionA token with no signature is accepted as proof of identity, so a forged token would likely stand in for real credentials.

How to use this: ask your IT provider which control or log would show each step, for example whether sign-in attempts from the internet are recorded. If nobody can answer, that is the gap to close first.

MITRE ATT&CK® is a registered trademark of The MITRE Corporation. Technique names are MITRE's.

The sources, in their words

The CVE record:

An improper JWT signature verification vulnerability in CIRCUTOR PowerStudio SCADA WAVE desktop version allows an unauthenticated remote attacker to bypass authentication by submitting an unsigned JWT with the algorithm set to “none”. The shared JWT validation component accepts the token without verifying a cryptographic signature, allowing the attacker to impersonate another user and access protected functionality with that user's privileges.

Versions of Circutor PowerStudio SCADA Wave the record lists as affected:

  • 24.8.0 up to, but not including, 24.11.17.0

It lists these as unaffected:

  • 24.11.17.0

What the record says to do about it, in the vendor's words:

Update CIRCUTOR PowerStudio SCADA WAVE to version v24.11.17.0 or later.

Check your own project

If you build software, you can compare what a project declares with this CVE from a terminal. The tool reads requirements files, package.json, Maven, Gradle, Cargo, CMake and Dockerfile files, runs nothing, and only the CVE id leaves your machine. Naming the CVEs needs no key.

lattice-scan project . --cve CVE-2026-120387

Each row says in-range, outside-range, undetermined or lead, with the file and line. That is evidence about what a manifest declares, not about what runs, and a person decides. The verdicts, the CSV columns and a pipeline recipe are in the guide.

Check the servers you run

The same id can be checked against a host. Run this on the machine itself, not on the laptop that deploys to it: it reads installed packages (dpkg, rpm or apk), snaps, the hardware (maker, model, firmware), the running container images with their operating system and packages, and the kernel version, compares them on the spot, and only the CVE ids leave the machine; the inventory stays on it, in ~/.lattice-scan. Naming the CVEs needs no key. Do it on each server after a deployment, and again when a new entry lands.

lattice-scan --cve CVE-2026-120387

A match is a candidate for a person to confirm, not a finding. A distribution can fix a CVE under an unchanged version number, so a match is a candidate; on Debian-family hosts the report also shows whether the package's own changelog names the CVE. By default it opens the images your containers are running and reads their operating system and package list; a deep scan (--deep, a few minutes) opens every local image and the Python, Node, Java and Ruby packages inside them; for what an image declares, use the project check on its Dockerfile.

Guide: namiq.io/lattice/guides/choose-your-channel. MCP server (io.namiq/lattice in the MCP registry): namiq.io/lattice. Package: pypi.org/project/lattice-scan, or namiq.io/apt.

What we do not know yet

  • Whether this flaw is being used in attacks. The record is new and CISA did not list it when we read it.
  • Which functions an impersonated user can reach, and whether an administrator can be impersonated.
  • How the desktop version is exposed to a network, and on which port.
  • Whether the vendor has published a separate advisory for this CVE. The page we read gives no detail.
  • Exploitation is not recorded. That is not the same as none.
  • This is a new record: scores, versions and wording can change in the first days, and they are as at 17 November 2026. We read the vendor pages listed under Sources; nothing here has been tested.
  • The sections headed "The bottom line", "Does this apply to you?", "What it is", "Why it matters", "Exposure by situation", "Things people will get wrong", "Likely ATT&CK mapping", "How we would triage it" and "Send this to your IT provider" are our interpretation of the sources, not a statement by CISA or the vendor.

Does this touch your business?

A new vulnerability is a question about what you run, who can reach it and what it would cost you. If you want a person to answer it for your own systems, start with your IT setup.

Also worth reading

Start with one piece of work.

Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.

Talk to us