- ASUS released Control Center Express v1.7.29 to fix three flaws. BleepingComputer reports one, CVE-2026-114202, scores CVSS 10.0 and needs no login.
- Management consoles hold admin rights over every device they run, so a flaw in one reaches the whole fleet.
- Teams should install v1.7.29, update the agents on managed PCs, and check which accounts and versions they run.
The tool that manages everything
Every company has a few systems that hold power over all the others. A fleet management console is one of them. It can see each PC, change settings and push updates. Whoever controls the console controls the fleet.
That is why the latest ASUS advisories deserve attention from the people who sign security budgets. The idea is simple. The more devices a tool can reach, the more its own flaws are worth to an attacker.
What ASUS fixed
ASUS shipped Control Center Express v1.7.29 and, according to BleepingComputer on November 19, it closes three flaws that carry a critical rating. The product is a single dashboard where IT staff watch over company PCs and manage them from afar.
The most serious is CVE-2026-114202. BleepingComputer reports a CVSS score of 10.0, the top of the scale. The cause is a hard-coded cryptographic key in the product.
The outlet says an attacker on the network, with no account, can forge a login token and become an administrator. No user has to click anything.
The second flaw, CVE-2026-114204, is also a hard-coded key problem. An outsider with low privileges can forge a session token for someone who logged in recently.
The third, CVE-2026-114205, is an authorization flaw. Someone with a low-level account can create an administrator account.
How a hard-coded key breaks trust
When a user logs in, the server hands back a signed token. Think of it as a stamped pass. The server accepts any pass that carries its own stamp.
A hard-coded key is built into the product itself. So it is typically the same across installations of that build. Anyone who recovers the key could print a pass the server accepts as genuine.
BleepingComputer does not say how an attacker would obtain the key. It also does not say whether anyone has used these flaws in attacks. Both questions remain open.
The three flaws also differ in what they demand. CVE-2026-114204 needs a target who logged in recently. CVE-2026-114205 needs a low-privilege account. CVE-2026-114202 needs nothing. That difference should set the order in which teams respond.
Other ASUS patches the same day
BleepingComputer also reports a fix in Control Center Enterprise. CVE-2026-126574 lets a remote user with only the Viewer role reset an administrator's password and take over that account.
Per BleepingComputer, the older releases at risk are Datacenter up to 4.0.0.2 and Enterprise up to 3.1.0.8. Teams on either line should check where they stand against those numbers.
ASUS also patched CVE-2026-112115 in Armoury Crate, a utility for configuring hardware. BleepingComputer rates it high severity. A local user with few rights could fool a process running with elevated rights into loading a malicious library.
These are separate products and separate flaws. Together they make one point. The tools that administer machines deserve the same scrutiny as the machines.
One gap in the version story
ASUS's bulletin names every version before v1.7.29 as affected. The CVE records, BleepingComputer notes, stop at v1.7.27. That leaves v1.7.28 unclear.
A team on v1.7.28 should not read the gap as a sign of safety. The prudent course is to treat that version as affected until ASUS says otherwise.
What to ask your team
BleepingComputer advises affected users to install v1.7.29. After that, they should push the update to the agents on managed devices and confirm the versions. In the console, that path runs through Select Function and Client Agent Updater. Updating the console alone does not finish the job.
Leaders can put five questions to their IT group this week.
First, do we run Control Center Express, Enterprise or Datacenter, and on which versions? Second, have the agents on managed PCs been updated, and who checked? Third, can anyone reach the console from outside our network, and does that need to be true?
Fourth, who holds low-privilege or Viewer accounts, given that two of these flaws start there? Fifth, can we review recent administrator account creations and password changes in the console?
ASUS's advisory page says the company follows coordinated vulnerability disclosure and scores issues with CVSS. It urges customers to keep products updated and to apply the latest patches. It also keeps a list of fixed issues. That list deserves a regular check, not only a look after a headline.
The takeaway
A fleet console is a master key to the fleet. A key printed into the product, and typically the same across installations of that build, makes a weak lock for that door. The patch fixes this product. The lasting habit is to list the tools that hold administrative power and patch them first.
Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: ASUS.





