ASUS has released Control Center Express 1.7.29 to repair three routes to administrative control. The product centrally monitors and manages PCs, so a compromised console can affect its managed clients. Install the console update, update the client agents, and verify their versions.
Bill Toulas reported the release on November 19. ASUS’s first-party bulletin, also available in its official advisory RSS, was published November 18. Its title is Security Update for ASUS Control Center Express Agent.
Three flaws have different access conditions
The ASUS-issued CVE records distinguish the attack paths:
- CVE-2026-114202: A cryptographic key embedded in the product permits forged authentication tokens and administrative privileges. ASUS rates this path as remotely reachable without an existing account or user interaction.
- CVE-2026-114204: Another embedded-key flaw allows forging a session token for an account with a recent valid login. Its severity vector also specifies low privileges as a prerequisite.
- CVE-2026-114205: An authorization error lets a low-privileged authenticated user create an administrator account, gaining control of the console and clients.
An authentication token is a credential the server accepts as evidence of a login. An embedded signing key undermines that evidence if an attacker can use it to manufacture an accepted token. Changing one user’s password does not replace the vulnerable product’s key handling.
These flaws concern Control Center Express, not every ASUS motherboard or a generic Windows vulnerability. The relevant exposure is a deployed management service reachable by an attacker. Two of the three paths also require the account or session conditions above.
Evidence status: vendor-confirmed vulnerabilities, with no in-the-wild exploitation reported in the reviewed bulletin or reporting. The records’ CISA enrichment labels exploitation none at its recorded assessment times. That is an assessment snapshot, not proof that every installation remains untouched.
Follow the bulletin’s repair target despite the range discrepancy
ASUS’s bulletin says versions earlier than 1.7.29 are affected. Its three CVE records list affected versions through 1.7.27, with a default status of unaffected outside that description. BleepingComputer flags the resulting uncertainty around 1.7.28.
Use 1.7.29 or later as the repair target. The broader bulletin is explicit, so the narrower CVE range is a poor basis for declaring 1.7.28 safe. The reviewed sources do not resolve the discrepancy.
The official bulletin gives a two-stage update procedure:
- Download and install Control Center Express 1.7.29 or later from ASUS’s official download page.
- Select the target devices in the device list.
- Choose “Select Function” → “Client Agent Updater” to update their agents.
- Verify that the agent version shows the updated version.
This last step matters because the management server and the managed machines are separate update targets. A repaired console does not by itself prove that every client has received the agent update. The bulletin does not give a separate numerical client-agent build, so verify against the update supplied by ASUS rather than inventing one.
Review administrative changes as well as update completion
The reported impacts include forged sessions and unauthorized administrator creation. Restrict console access to approved management clients while applying the repair. Review administrative accounts and management activity against authorized work if earlier exposure raises concern.
Those are defensive implications of the documented capabilities, not a claim that ASUS has identified a breach at a particular customer. If unauthorized administrative access is found, an update is only one part of recovery. Investigate actions on managed endpoints and revoke attacker-created access.
ASUS also published separate updates for Control Center Enterprise/Datacenter and Armoury Crate. Their vulnerabilities, version ranges and repair procedures differ. This Express update should not be treated as a blanket repair for those products.
Caveat: The vendor bulletin and CVE records disagree about the affected range around 1.7.28; both the console and client-agent update steps still need verification.