ASUS released Control Center Express v1.7.29, and BleepingComputer reports that the update addresses CVE-2026-114204, CVE-2026-114202 and CVE-2026-114205, an authorization flaw that lets a low-privileged user create an administrator account. The CVE records were published on November 18, 2026, the same day as ASUS's advisory batch.
What Control Center Express does, and why that raises the stakes
ASUS Control Center Express is a central dashboard that IT administrators use to monitor and remotely manage fleets of PCs. BleepingComputer says ASUS sells it to businesses and IT service providers and lists support for more than 200 of its business, workstation and Corporate Stable Model motherboards.
That is why these bugs matter more than a typical app flaw. An attacker who takes over a management console also gets the tools it uses to control other machines. Two of the CVE descriptions say this directly: a successful attack gives control of the management console and of the clients it manages. One threat-intelligence summary puts it this way: "Successful exploitation grants administrative control over the management console and the clients it manages."
Section summary: This isn't one compromised PC. It's a compromised control point for every PC the console manages.
The three vulnerabilities
| CVE | Weakness | CVSS 4.0 (ASUS as CNA) | Attacker needs |
|---|---|---|---|
| CVE-2026-114202 | Hard-coded cryptographic key (CWE-321) | 10.0 | Network access only. No account, no user interaction |
| CVE-2026-114204 | Hard-coded cryptographic key (CWE-321) | 9.0 | Low privileges, plus a target account with a recent valid login |
| CVE-2026-114205 | Incorrect authorization | 9.4 | A low-privileged authenticated account |
CVE-2026-114202: the maximum-severity one
The CVE record published by ASUS, as shown on Secure.com's CVE tracker, says a hard-coded cryptographic key in Control Center Express lets a remote user gain administrative privileges with a forged authentication token. The record carries a CVSS 4.0 score of 10.0 and lists versions through v1.7.27 as affected. When Secure.com last checked, the flaw was not in CISA's Known Exploited Vulnerabilities catalog.
Why hard-coded keys are so bad (general industry background, not taken from ASUS's advisory): When a key that signs or validates tokens is built into the product, every installation typically shares the same secret. Anyone who extracts it from one copy can create valid-looking credentials for every other copy. It's like a building where every apartment door opens with the same key, and that key is taped inside the brochure.
CVE-2026-114204: the second hard-coded key, with a catch
The CVE description says the hard-coded key allows a remote user to bypass authentication by forging a session token for an account with a recent valid login, resulting in administrative control of the management console and of its clients. ASUS's CNA score is CRITICAL: 9.0, with the vector CVSS:4.0/AV:N/AC:L/AT😛/PR:L/UI:N. The "AT😛" (attack requirements present) and "PR:L" (low privileges required) parts of that vector match the recent-session prerequisite BleepingComputer describes.
Third-party databases don't fully agree here. VulDB's entry gives a 10.0 base score and says no form of authentication is needed for exploitation. The vendor's own CVSS vector says low privileges are required. This article follows ASUS's vector. Treat the gap as one more reason not to delay the patch, since both readings rate the bug critical.
CVE-2026-114205: low-privileged user to admin
According to the record on OpenAdvisories, this incorrect-authorization flaw lets a remote, authenticated user with a low-privileged role create an administrator account. That gives the attacker control of the console and its managed clients. It scores 9.4 under CVSS 4.0. On the practical risk, consider a shared helpdesk login, a contractor account or a phished junior technician. Any of them can now become an attacker with full admin rights.
Section summary: While all three vulnerabilities are rated critical, CVE-2026-114204 has a recent-session prerequisite, and CVE-2026-114205 requires a low-privileged account, whereas CVE-2026-114202 enables remote administrative access with no prerequisites.
Which versions are affected? It depends on the source
ASUS's security bulletin says versions earlier than v1.7.29 are affected. However, the CVE records only list affected versions through v1.7.27, leaving the status of v1.7.28 unclear. Independent trackers show the same CVE range. OpenCVE, for example, lists versions up to and including 1.7.27.
The available records don't explain the difference. The safe reading is ASUS's broader advisory statement: if you're on anything older than v1.7.29, including v1.7.28, treat the system as vulnerable. No published source confirms that v1.7.28 is safe.
Is it being exploited?
None of the sources reviewed here reports exploitation in the wild or a public proof-of-concept. OffSeq's tracker lists CVE-2026-114204 as "Not known to be exploited". CyStack's ASUS vulnerability summary reported 0 known exploited vulnerabilities (KEV) across ASUS products as of November 18.
Still, the flaws are now public, and two of them come down to a key baked into software anyone can download. Researchers and attackers can both pull that software apart and study it. Patching quickly is the sensible move.
What admins should do
The vendor-aligned steps reported by BleepingComputer: install v1.7.29, then update the agents on managed devices through Select Function → Client Agent Updater, and verify their versions.
- Inventory. Find every Control Center Express console in your environment, including any your MSP or a branch office set up and nobody wrote down.
- Upgrade the console to v1.7.29. Every earlier version should be treated as affected, as explained above.
- Push the agent update. In the console, select the managed devices, go to Select Function → Client Agent Updater, and run it. ASUS labels its advisory section "Security Update for ASUS Control Center Express Agent," so the managed agents need updating too. Don't assume upgrading the console takes care of them.
- Verify. Check that the managed devices actually report the updated agent version, rather than assuming the push worked on every machine.
- Limit exposure until you've patched. OpenCVE's mitigation guidance recommends that you disable or restrict remote access to the Control Center Express system until the update is applied. If the console can be reached from the internet, close that off now.
Post-patch hygiene (general incident-response practice, not ASUS guidance): CVE-2026-114205 lets attackers create admin accounts. After patching, review the console's administrator list for accounts nobody remembers creating. Check recently dispatched software and remote sessions for anything unexpected. If you suspect someone has already been in, rotate the credentials for legitimate admin accounts.
The same advisory batch: Control Center Enterprise, Datacenter and Armoury Crate
ASUS also fixed flaws in two other products in the same round. They are separate from the Express fixes, so updating to v1.7.29 doesn't cover them.
- CVE-2026-126574 (Control Center Datacenter and Enterprise): According to the CVE record on Secure.com, this missing-authorization bug (CWE-862) lets a remote, authenticated user with the low-privileged Viewer role send a crafted password-update request. That request changes an Administrator account's password, and the attacker gets admin privileges. It scores 9.4 under CVSS 4.0 and affects Control Center Datacenter 4.0.0.2 and earlier and Control Center Enterprise 3.1.0.8 and earlier. The sources reviewed don't state the fixed version numbers, so check ASUS's advisory for the right build.
- CVE-2026-112115 (Armoury Crate): BleepingComputer reports a high-severity privilege-escalation flaw affecting versions up to and including 6.7.2. A low-privileged local user could trick an elevated process into loading a malicious library. Armoury Crate is common on ASUS consumer and gaming PCs, so home users who never touch fleet-management software should update it too.
The bigger picture
Remote management tools have long been a favorite target. Attackers who break into the software admins use to control many machines can reach all of those machines at once. ASUS's three bugs fit a familiar pattern. Two come from a secret that should never have been the same across installations, and the third is a role check that doesn't actually stop a low-privileged user.
Credit where it's due: ASUS published CVEs with full CVSS 4.0 vectors and shipped a fix at the same time it disclosed. The mismatch between "prior to v1.7.29" and "through v1.7.27" is a documentation gap ASUS should clear up, because admins on v1.7.28 shouldn't have to guess whether they're exposed.
Bottom line: If you run Control Center Express, update the console to v1.7.29, push the agent update, confirm the versions on your managed devices and check for unfamiliar admin accounts. If you also run Control Center Enterprise or Datacenter, or have Armoury Crate on your ASUS PCs, update those as well.
References
- ASUS warns of critical hard-coded key flaw in Control Center Express BleepingComputer · 2026-11-19T16:15:59-05:00
- CVE-2026-114204 ASUS Control Center Express hard-coded credentials vuldb.com
- CVE-2026-114204: Control Center Express · Use of Hard-coded… radar.offseq.com