Key Takeaways
- Three Critical Flaws: ASUS patched three critical Control Center Express flaws on November 18, 2026, including CVE-2026-114202, which scores 10.0 and allows administrator access without a login. No exploitation had been reported as of November 20, but you should still patch.
- Check Your Exposure: ASUS Control Center Express mainly serves business IT teams, so your home ASUS laptop probably does not run the software. If you manage PCs through ACCE, check both the console version and the agents installed across your computers.
- Patch Every Layer: Install ASUS Control Center Express v1.7.29 or later, then run Select function > Client Agent Updater and verify agent versions, retrying offline PCs. If you do not use ACCE, check Armoury Crate, MyASUS components and your ASUS router for updates.
If you manage ASUS PCs for a business, the ASUS Control Center Express flaw deserves your attention today. On November 18, 2026, ASUS released fixes for three critical vulnerabilities in its business PC management software. The most serious, CVE-2026-114202, scores the maximum 10.0 and lets a remote attacker forge an administrator token without a login.
Your fix is version 1.7.29 or later, followed by updates to the agents on your managed PCs. No exploitation has been reported as of November 20. That gives you a chance to patch before reported attacks, but it is no reason to put the update off. If you want to see how a similar admin console flaw played out, read our guide to the FortiMail vulnerability.
Using an ASUS laptop at home? You probably do not have Control Center Express installed, since ASUS targets business customers and providers of IT services. You should still install the separate Armoury Crate update if you use that application. First, here are the details that tell you whether this warning applies to your setup.
| Item | Details |
|---|---|
| Product | ASUS Control Center Express, also called ACCE |
| CVEs | CVE-2026-114202, CVE-2026-114204 and CVE-2026-114205 |
| Top CVSS | 10.0 under CVSS 4.0 |
| Affected versions | ASUS advises updating anything before v1.7.29. CVE records list versions through v1.7.27, leaving v1.7.28 unclear |
| Fixed version | v1.7.29 or later |
| Patch date | November 18, 2026 |
| Exploited? | No reported exploitation as of November 20 |
| Who needs to act | IT administrators running ACCE and managing PCs through its agents |
Who Actually Runs ASUS Control Center Express
ASUS Control Center Express gives your IT team a central console for monitoring and managing groups of computers. You can use it for remote desktop access, BIOS updates, power control and software deployment. Those capabilities explain why access to the console matters so much.
ASUS lists support for more than 200 business, workstation and CSM motherboards, and some ASUS business products come with an ACCE license. That business audience is why your personal ROG, TUF, Zenbook or Vivobook probably does not have it, although the model name alone cannot confirm that. Check how your computer is managed against these clues.
You probably have it if…
- Your IT team uses an ASUS console to control multiple computers remotely.
- Your organization deploys software or BIOS updates through ACCE.
- Your business purchased compatible ASUS hardware with an included ACCE license and put that license into use.
What the ASUS Control Center Express Flaw Lets an Attacker Do
The three vulnerabilities create different routes to administrator access. One requires no account, while the other two require an attacker to already have limited access. Here is what separates them.
| CVE | CVSS 4.0 score | What it allows | What the attacker needs |
|---|---|---|---|
| CVE-2026-114202 | 10.0, Critical | Forge an authentication token and obtain administrator privileges | Network access to the vulnerable service, with no login or user interaction |
| CVE-2026-114204 | 9.0, Critical | Forge a session token for an account that recently logged in, gaining administrator control | A low-privilege account and a recent valid login for the account being impersonated |
| CVE-2026-114205 | 9.4, Critical | Create an administrator account through faulty authorization checks | An authenticated account with low privileges |
The first two bugs involve hard-coded cryptographic keys. That means a secret used to establish trust is built into copies of the software, rather than being unique to your installation. Anyone who extracts that shared secret can use it to produce tokens the vulnerable software accepts.
The Perfect 10 That Needs No Password
CVE-2026-114202 is the most urgent because an attacker does not need your password or an existing account. The attack works over a network and requires no action from you or another user. A forged authentication token can give the attacker administrator privileges.
Here’s the thing. A login screen cannot protect the console properly when the software accepts a token an attacker created. That is why checking passwords alone does not address this flaw.
Two Follow-On Holes for Logged-In Users
CVE-2026-114204 has an extra condition. With a low-privilege account, an attacker can fabricate a session token impersonating a user who recently signed in successfully, then take administrator control over your console and its managed computers. Its 9.0 score still places it in the critical category.
CVE-2026-114205 takes a different route. Faulty authorization checks let a low-privilege user create an administrator account, earning it a 9.4 score. You therefore need the update even if you believe every existing ACCE account belongs to someone you trust.
Why One Console Puts Every Managed PC at Risk
Your ACCE console can reach beyond the server where it runs. Its remote desktop, BIOS update and software deployment functions give administrators substantial control over connected computers. An attacker who gains those privileges could put the managed fleet at risk.
That does not mean every connected PC has been compromised. It means your response needs to cover the management server and its endpoint agents, because updating the console alone does not update those agents.
Has Anyone Been Hit Yet
No exploitation has been reported as of November 20, and public tracking reports list no public proof-of-concept exploit code. Third-party trackers also report no listing in CISA’s Known Exploited Vulnerabilities catalog. Those findings describe the current reporting, so treat them as context for patching rather than reassurance that you can wait.
The reported EPSS estimates are about 0.38% for CVE-2026-114202 and 0.35% for CVE-2026-114204. These are estimates of exploitation over 30 days, separate from the severity scores. The CVE records credit researcher 0x0dee with all three ACCE vulnerabilities.
Hard-coded secrets can be reverse-engineered quickly after a patch becomes available. With a fix already available, your next step is to check which versions your server and clients actually run.
How to Check Which Version You’re On
You need two checks here, one for the main ACCE console and another for the agents installed on managed computers. A current server version does not prove that every client has received its update. Start with the console, then work through the device list.
On the ACCE Console
- Sign in to your ACCE console and open its configuration menu.
- Choose Options > General Configuration.
- Scroll down to Appearance Configuration and read the displayed server version.
- Plan an update to v1.7.29 or later if your installation is older.
ASUS’s bulletin covers versions before v1.7.29, while the CVE records stop at v1.7.27. Do not assume v1.7.28 is safe because of that gap. Move to v1.7.29 or later regardless.
These menu labels come from ASUS’s October 2024 manual, which predates the patch. Your installation may show slightly different wording.
On Each Managed PC
- Open the console’s device list.
- Check the Agent Version column for each managed computer.
- Alternatively, open a client’s Device Information page to read its agent version.
- Identify clients that still need the agent update, even if you have already updated the server.
On a Single Windows PC
- Open Apps & features on the computer.
- Look for ASUS Control Center Express Manual Deploy.
- If that entry appears, your PC has the manually deployed Windows agent described in ASUS’s manual.
That application entry helps you identify a manually installed agent. Its absence alone does not establish that your computer is unmanaged, so use the console’s device list when you have access to it.
Steps to Update to Version 1.7.29
Your update has two parts, the server installation and the agents on your managed computers. Complete both using the sequence below.
- Download ASUS Control Center Express v1.7.29 or later from ASUS’s official download page.
- Install the new version on your main ACCE server.
- In the console’s device list, select the computers whose agents you want to update.
- Choose Select function > Client Agent Updater, then click Yes.
- Open the Mission Center to track the update tasks.
- Check the Agent Version column or each client’s Device Information page to confirm that the agents received the update.
Only online computers can receive the agent update. Offline devices show a failed task, so retry those computers after they reconnect.
Updating your console does not update the endpoint agents automatically. Keep checking your device list until you have accounted for every managed computer.
Removing the Agent If You Don’t Use It
If you no longer use ACCE to manage a computer, you can remove its agent. For a manually installed Windows agent, begin in the server console before uninstalling anything locally.
- Open Agent Management on your ACCE server.
- Select the devices you want to remove.
- Click the Remove icon, then confirm with OK.
- On each Windows PC with a manually deployed agent, open Apps & features.
- Select ASUS Control Center Express Manual Deploy and choose Uninstall.
If a selected device is offline, its removal takes place when it reconnects. Linux clients need no additional local uninstall step after removal through the server.
Extra Hardening for IT Teams
Patching closes the reported vulnerabilities, but you should also check who can reach your console and what has happened inside it. Work through these checks alongside the update.
- Keep console access restricted. Avoid exposing ACCE directly to the public internet.
- Audit administrator accounts. Check for unfamiliar accounts and unexpected password changes.
- Review authentication logs. Look through recorded logins for activity you cannot explain.
- Replace unchanged default credentials. ASUS’s manual documents administrator as the default username and admin as the default password, and instructs you to change them.
- Check other ASUS management software. Control Center Enterprise and Datacenter have a separate critical flaw, CVE-2026-126574, that lets a low-privilege user change an administrator’s password.
That separate vulnerability affects Datacenter 4.0.0.2 and earlier, plus Enterprise 3.1.0.8 and earlier. ASUS advises installing the latest release without naming a fixed version in its bulletin, so do not assume the ACCE installer covers those products.
The ASUS Updates Home Users Should Install Instead
If your personal ASUS computer does not run ACCE, you probably have a different update list to work through. ASUS issued separate November 18 fixes for consumer utilities and router firmware, so check the products you actually use.
| Product | CVE | Score | How to update |
|---|---|---|---|
| Armoury Crate | CVE-2026-112115 | 8.5 | Open its configuration menu, then Update Center > Check for Updates > Update |
| ASUS System Control Interface | CVE-2026-112117 | 7.3 | Use MyASUS, ASUS Support or Windows Update |
| DisplayWidget Center | CVE-2026-119469 | 7.0 | Install v1.5.2.8 or later |
| ASUS router firmware | CVE-2026-19399, CVE-2026-88711, CVE-2026-88760, CVE-2026-93458 and CVE-2026-93459 | 5.3 to 8.7 | Install the latest firmware available for your router |
Updates for Your ASUS PC
The Armoury Crate vulnerability involves an elevated process being tricked into loading a malicious library. Reporting lists versions through 6.7.2 as affected, but ASUS’s bulletin gives no fixed version number. Use the application’s updater rather than guessing which build you need.
For System Control Interface, use one of ASUS’s supported update routes listed above. If you use DisplayWidget Center, confirm that the installed version is at least 1.5.2.8.
Router Updates and Your Next Steps
Your router deserves a check too. ASUS’s interim guidance includes disabling iTunes Server and remote file access, and avoiding untrusted links while signed in to the router.
If you run ACCE, update your server and agents today, then verify the results. If you do not, check Armoury Crate and the ASUS components available through MyASUS so your next update session covers the software you actually have.
FAQs
You can look in Apps & features for ASUS Control Center Express Manual Deploy to identify a manually installed Windows agent. If your IT team manages the computer, you can also check its entry in the ACCE device list. That console shows the agent version, while the client’s Device Information page provides another way to check.
Your gaming laptop probably does not run ACCE, but you need to check the installed software to be sure. ASUS markets ACCE to businesses, so owning a ROG or TUF laptop alone does not establish that you have the vulnerable software. If your computer has an ACCE agent, include it in your update checks.
No exploitation has been reported as of November 20, 2026. Public tracking reports also list no public exploit code. You should still patch because the most serious flaw requires neither an account nor user interaction.
You should install v1.7.29 or later. ASUS advises updating versions before that release, even though the CVE records list affected builds only through v1.7.27. The uncertainty around v1.7.28 is a reason to update rather than assume it is safe.
No, updating your ACCE console does not automatically update the agents on your computers. Select your target devices and run Select function > Client Agent Updater. Check the resulting agent versions and retry any computers that were offline.
Yes, if you use Armoury Crate, you should install its separate security update. Open its configuration menu and choose Update Center > Check for Updates > Update. That addresses CVE-2026-112115, a different vulnerability from the three ACCE flaws.

