top of page

ASUS Control Center Express Ships a Hard-Coded Key That Lets a Stranger on the Network Forge an Admin Token. Update the Console and Every Agent to 1.7.29

Writer: Patrick Duggan
Patrick Duggan
13 minutes ago
4 min read

What to do first. If your IT team manages ASUS business PCs with ASUS Control Center Express (ACCE), update it to version 1.7.29 or later today, then push the update to the client agent on every managed PC. Until that is done, make sure the ACCE console cannot be reached from the internet or from guest and user Wi-Fi segments: the worst of the three flaws needs no password at all, only network access. A management console that can run commands on every PC in the building is the last thing you want a stranger to log into as administrator.



What ASUS confirmed


ASUS published a bulletin titled "Security Update for ASUS Control Center Express Agent" in its security advisory feed on November 18, 2026 (10:29 Taipei time, 02:29 UTC). It says the update fixes flaws affecting versions earlier than v1.7.29 that could allow a remote user "to bypass authentication or improperly" gain access. The feed lists three CVEs, all rated Critical under CVSS 4.0:


  • CVE-2026-114202, CVSS 10.0. A hard-coded cryptographic key. Network attack, no account, no user interaction. BleepingComputer describes the result as an unauthenticated attacker forging an authentication token and getting administrator rights.

  • CVE-2026-114204, CVSS 9.0. Also a hard-coded key. Needs a low-privileged account and a precondition (the vector says AT:P). BleepingComputer says it lets that user forge a session token for an account that logged in recently.

  • CVE-2026-114205, CVSS 9.4. An authorization flaw. A low-privileged user can create an administrator account, per BleepingComputer.

ACCE is the dashboard IT administrators use to monitor and remotely manage fleets of ASUS PCs. BleepingComputer reports ASUS lists support for more than 200 business, workstation and Corporate Stable Model motherboards. It is a small and mid-size business tool much more than a home one, which is exactly the population with no one watching the console at night.



How to update, per ASUS


  1. Download and install ACCE v1.7.29 or later from the official ACCE download page.

  2. In the console, select the target devices in the device list.

  3. Choose "Select Function", then "Client Agent Updater", to update the agents.

  4. Check that each agent now reports the new version.

The console and the agents are separate pieces of software. Updating the console alone leaves the agent on each PC on the old version.



What is not known


  • Exploitation. Neither ASUS nor BleepingComputer reports attacks in the wild, and we found no public proof-of-concept. CVE-2026-114202 is not in CISA's KEV catalog as of November 19. A hard-coded key, though, is the same in every copy of the software: once someone extracts it from one install, it works against all unpatched ones. Do not wait for a KEV entry.

  • Which key, protecting what. The ASUS bulletin does not say. The "forge a token" description is BleepingComputer's.

  • Version 1.7.28. BleepingComputer notes the ASUS bulletin says "earlier than v1.7.29" while the CVE records list affected versions only through 1.7.27. We could not read the CVE or NVD records (both pages returned only an empty shell to our fetch). Treat 1.7.28 as affected and go to 1.7.29.

  • Who found it. No researcher is credited in the bulletin or the article.


Other ASUS fixes the same day


The same ASUS feed published, on the same date, a fix for ASUS Control Center Enterprise and Datacenter (CVE-2026-126574, CVSS 4.0 9.4: a low-privileged Viewer account can reset an administrator password; affects Datacenter 4.0.0.2 and earlier, Enterprise 3.1.0.8 and earlier) and for Armoury Crate (CVE-2026-112115, local privilege escalation, through 6.7.2). If you run the bigger Control Center products, update those too.



Am I affected? A self-check


  • In the ACCE console, check the version shown in the About or Settings page. Anything below 1.7.29 is affected.

  • In the device list, look at the agent version for each managed PC. Any agent below 1.7.29 still needs the Client Agent Updater step.

  • Check where the console listens. If its address is reachable from the internet, from a guest network or from any user VLAN, restrict it to the IT admin network with a firewall rule now, and keep that rule after patching.

  • Review the console's administrator accounts. An admin account you did not create is the sign you would expect from CVE-2026-114205. If you find one, treat every managed PC as possibly touched, not just the console.


Indicators


None published in the sources we read. ASUS and BleepingComputer give no attacker IP addresses, domains or file hashes, so we added nothing to the feed. Our "Am I affected?" site checker does not apply: this is a flaw in management software inside your network, not a script loaded on a homepage.



Sources


  • ASUS security advisory feed, item "Security Update for ASUS Control Center Express Agent", November 18, 2026: https://security-advisory-api.asus.com/rss/securityrss.xml (linked from https://www.asus.com/security-advisory/, whose bulletin table did not render for our fetch)

  • BleepingComputer, "ASUS warns of critical hard-coded key flaw in Control Center Express" (November 19, 2026): https://www.bleepingcomputer.com/news/security/asus-warns-of-critical-hard-coded-key-flaw-in-control-center-express/

  • CISA KEV JSON (checked November 19, 2026: CVE-2026-114202 not listed)


Get exploited-bug coverage and a blocklist you can pull for free: register for the DugganUSA feed (docs at docs.dugganusa.com).




Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.


Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page