Are your ASUS Control Center or Control Center Express consoles exposed to CVE-2026-114202?
ASUS published 18 November 2026 security bulletins for Control Center Express and for Control Center Datacenter and Enterprise. The official CVE record for CVE-2026-114202, assigned by ASUS, describes use of a hard-coded cryptographic key in Control Center Express. It allows a remote user to gain administrative privileges via a forged authentication token. ASUS, as the CNA, scores it CVSS 4.0 10.0 Critical. Upgrade Control Center Express to v1.7.29 or later, then update the client agents. Upgrade Control Center Datacenter and Enterprise to the latest version ASUS provides.
Critical (CVSS 4.0 10.0). Not in CISA KEV when we checked
ASUS, as the CNA, scores CVE-2026-114202 CVSS 4.0 10.0 Critical. Related Express issues are scored 9.0 and 9.4 Critical, and the Control Center Datacenter and Enterprise issue is scored 9.4 Critical. None of the four CVEs was in CISA's Known Exploited Vulnerabilities catalogue when we checked at 02:32 GMT on 18 November 2026 (catalogue 2026.11.17, released 17:53 GMT on 17 November 2026). We do not treat absence from KEV as proof that the flaws have been used. Recheck KEV. We do not link proof-of-concept or exploit code.
By Simon Phillips, CTO. Reviewed by Oliver Legg, Head of SOC and IR. Last updated 18 November 2026, 18:09 GMT.
At a Glance
ASUS Control Center Express, Control Center Datacenter and Control Center Enterprise are management consoles. The official CVE records say that, if exploited, these issues can give administrative control of the console and of the clients it manages. NVD published all four CVE records at 02:17 GMT on 18 November 2026, status Received, repeating ASUS's descriptions and CVSS 4.0 scores. ASUS's Security Advisory lists both bulletins on 18 November 2026. The Control Center Express Agent bulletin carries a published time of 02:29 GMT that day.
| CVE | Product | Score (ASUS CNA, CVSS 4.0 only) | CWE | What the official record says | Affected / fix |
|---|---|---|---|---|---|
| CVE-2026-114202 | ASUS Control Center Express only | 10.0 Critical | CWE-321 | Use of a hard-coded cryptographic key allows a remote user to gain administrative privileges via a forged authentication token. The CVSS 4.0 vector sets Privileges Required to None. | Bulletin: versions earlier than v1.7.29, so v1.7.28 counts as affected; install v1.7.29 or later, then update agents. CVE record: affected through v1.7.27. |
| CVE-2026-114204 | ASUS Control Center Express only | 9.0 Critical | CWE-321 | Use of a hard-coded cryptographic 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 console and the clients it manages. The CVSS 4.0 vector sets Attack Requirements to Present and Privileges Required to Low. This issue is not described as needing no login. | Same Express bulletin and upgrade as above, including v1.7.28 as affected under the bulletin. |
| CVE-2026-114205 | ASUS Control Center Express only | 9.4 Critical | CWE-863 | Incorrect authorization allows a remote authenticated user with a low-privileged role to create an administrator account, resulting in administrative control of the console and the clients it manages. | Same Express bulletin and upgrade as above, including v1.7.28 as affected under the bulletin. |
| CVE-2026-126574 | ASUS Control Center Datacenter and Control Center Enterprise only (the other three CVEs do not apply to these editions) | 9.4 Critical | CWE-862 | Missing authorization allows a remote authenticated user with a low-privileged Viewer role to change the password of an Administrator account, via a crafted password update request. | Datacenter 4.0.0.2 and earlier, Enterprise 3.1.0.8 and earlier. ASUS does not name an exact fixed build; upgrade to the latest version. |
ASUS's Express bulletin groups the three Express issues as allowing a remote user to bypass authentication or improperly gain administrator-level access to the management console and the clients it manages. We use that wording, and the more specific wording from each CVE record, rather than going beyond it.
Your next 24 hours
Find every console
Our advice: inventory every ASUS Control Center Express, Control Center Datacenter and Control Center Enterprise console you or your clients run, including those that are only used on a management network.
Patch the console, then the agents
Vendor advice (ASUS): for Control Center Express, download and install v1.7.29 or later (the bulletin treats versions earlier than v1.7.29, including v1.7.28, as in scope), then use Client Agent Updater to update the client agents and verify the agent version. ASUS does not name a fixed agent version. For Control Center Datacenter and Enterprise, upgrade to the latest version. Our advice: patch the console first, then the agents, and do not assume a console upgrade has already pushed every agent.
Keep consoles off the internet until they are patched
Our advice: until the console is patched, keep it off the public internet, on an admin VLAN or reachable only over VPN. Prune low-privileged console accounts you do not need. Because CVE-2026-114202 and CVE-2026-114204 involve a hard-coded cryptographic key, treat any console reachable from an untrusted network as exposed.
Proactive: Check and patch
Vendor advice
- ASUS Control Center Express: the 18 November 2026 Control Center Express Agent bulletin says to download and install v1.7.29 or later from the official ASUS Control Center Express download page, select the target devices in the device list, go to "Select Function" > "Client Agent Updater" to update the client agents, and verify that the agent version shows the updated version. The bulletin says this update addresses versions earlier than v1.7.29, so v1.7.28 counts as affected. ASUS does not name a fixed agent version; the required step is to run Client Agent Updater and verify the agent version.
- ASUS Control Center Datacenter and Enterprise: only CVE-2026-126574 applies to these editions. The 18 November 2026 Control Center bulletin lists Datacenter 4.0.0.2 and earlier, and Enterprise 3.1.0.8 and earlier, as affected, and strongly recommends upgrading ASUS Control Center to the latest version. It does not name an exact fixed build. Check the official ASUS Control Center download page for the latest package ASUS provides.
- The ASUS Control Center Express user manual (E24388, version 01.07, Account Settings) tells users to change the default administrator credentials.
- The official bulletins do not publish a workaround, indicators of compromise, or an exploitation status.
Our advice
- Inventory every Control Center Express, Datacenter and Enterprise console you or your clients run.
- Patch the console first, then push or confirm the agent update. For Express, follow ASUS's Client Agent Updater steps and check the agent version on each client.
- Until patched, keep consoles off the public internet, on an admin VLAN or reachable only over VPN, and prune low-privileged console accounts you do not need.
- Because two of the Express issues involve a hard-coded cryptographic key, treat any console reachable from an untrusted network as exposed, even after you have restricted access, until it is patched and credentials have been rotated.
The official CVE records for the three Express issues list affected versions as through v1.7.27. The ASUS bulletin tells users to install v1.7.29 or later and describes the issues as affecting versions earlier than v1.7.29, so v1.7.28 counts as affected under the bulletin. We follow the bulletin for the upgrade path, and we record the CVE wording so that operators can see the difference. We did not find an official statement that names a fixed build between v1.7.27 and v1.7.29.
Free Detection Pack
Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Check console and agent versions offline and hunt for signs of misuse. Everything is read-only. Pack version 1.0.0 is the download on this page. The KQL and Sigma have not been run against live data.
check-asus-acc.sh
Read-only offline checker, pack version 1.0.0. Unpack the full pack first, so scripts/ stays in place. It opens no sockets, writes no files, and runs no other program except tr, head and wc. It reads a console version, a saved installed-programs export, and an optional agent inventory CSV. It prints product names, versions and agent device names only. ASUS names no fixed agent version, so listed agents are marked REVIEW: run Client Agent Updater and verify the version shown.
bash scripts/check-asus-acc.sh --product express --version 1.7.27
bash scripts/check-asus-acc.sh --installed-file installed-programs.txt --agents-file agents.csvCheck-AsusAcc.ps1
The same checks in PowerShell 7, with identical output and exit codes. Run it from the unpacked full pack. It is also read-only, opens no sockets and writes no files.
pwsh -File scripts/Check-AsusAcc.ps1 -InstalledFile installed-programs.txt -AgentsFile agents.csvKQL and Sigma
6 KQL hunts for Microsoft Sentinel and Defender, all OUR PATTERN. The pack uses a 1-day lookback and a 30-day baseline (our choice). Q1 inventories consoles and agents in Defender software inventory. Q2 finds Control Center Express console hosts by process. Q3 looks for inbound connections from public addresses to the default console and agent ports documented in the ASUS Express user manual. Q4 looks for new local administrator accounts and Windows Security password-change events on console hosts and clients. Q5 looks for shells, script hosts or installers started from an ASUS Control Center folder. Q6 looks for public sources reaching the default console HTTPS port. 6 Sigma rules, all OUR PATTERN, with Kusto conversions included. ASUS publishes no indicators of compromise, so every hunt is OUR PATTERN, not a vendor IOC. The KQL and Sigma have not been run against live data. A hunt hit is a lead to investigate, not proof that these flaws were used. Console accounts are application accounts, so Windows Security events do not record console-account changes; review those in the console itself.
Verdicts
- NOT AFFECTEDEvery console found is at a build ASUS names as fixed, and no ACC agents are listed (exit 0).
- AFFECTEDAt least one console is in a range ASUS lists as affected (exit 2). For Express, that includes builds earlier than v1.7.29, so v1.7.28 is AFFECTED.
- UNKNOWNNo usable version, or a Datacenter or Enterprise build above the listed affected range, for which ASUS names no fixed build (REVIEW) (exit 3).
- AGENTS TO UPDATEConsoles are fixed, but ACC agents are listed and ASUS names no fixed agent version (REVIEW) (exit 4).
Exit codes
| Code | Meaning |
|---|---|
| 0 | NOT AFFECTED |
| 1 | Not used |
| 2 | AFFECTED |
| 3 | UNKNOWN or REVIEW |
| 4 | AGENTS TO UPDATE (REVIEW) |
| 5 | Usage or read error |
The full pack zip contains 39 files (pack version 1.0.0). For Express, the checker follows the ASUS bulletin, so v1.7.28 is AFFECTED. Datacenter and Enterprise builds above 4.0.0.2 and 3.1.0.8 are REVIEW, because ASUS names no fixed build.
Know the limits
- Both checkers are read-only and offline. They open no sockets, write no files and contain no exploit payloads.
- ASUS publishes no indicators of compromise. Every hunt and Sigma rule in this pack is OUR PATTERN, not a vendor IOC.
- A hunt hit is a lead to investigate. It does not prove that these flaws were used.
- The hunts use a 1-day lookback and a 30-day baseline. Those windows are our choice.
- None of the KQL or Sigma has been run against live data.
- Default console and agent ports used in the hunts come from the ASUS Control Center Express user manual and can be changed. Ports for Datacenter and Enterprise were not verified and are not used.
What is in the pack
| File | What it does |
|---|---|
| scripts/check-asus-acc.sh | Offline console and agent version checker for Linux and macOS (bash) |
| scripts/Check-AsusAcc.ps1 | The same checker in PowerShell 7 |
| KQL (6 hunts) | Microsoft Sentinel and Defender hunts Q1 to Q6, all OUR PATTERN |
| Sigma (6 rules) | All OUR PATTERN, plus Kusto conversions |
| tests/ | Fixtures, bash and Pester tests and static gates |
| README.md | Verified facts, vendor vs our advice, checker usage, limits and sources |
Reactive: How to hunt
ASUS publishes no indicators of compromise for these issues. Everything below is OUR PATTERN, not a vendor IOC. A hunt hit is a lead to investigate, not proof that these flaws were used.
- Administrator accounts on the console that you do not recognise.
- Unexpected changes to an Administrator account password, including changes made by a Viewer or other low-privileged account.
- Administrator sessions from unusual IP addresses.
- Tasks, software or agent actions pushed to managed clients that nobody approved.
If you find any of those: isolate the console from untrusted networks, patch it (and, for Express, update the agents), rotate all console credentials, check managed endpoints for software or tasks you did not approve, and rebuild where needed.
Questions people ask
What is CVE-2026-114202, and what else is covered on this page?
The official CVE record, assigned by ASUS, describes use of a hard-coded cryptographic key in ASUS Control Center Express. It allows a remote user to gain administrative privileges via a forged authentication token. ASUS, as the CNA, scores it CVSS 4.0 10.0 Critical. The same 18 November 2026 Express bulletin also covers CVE-2026-114204, where a remote user can forge a session token for an account with a recent valid login, and CVE-2026-114205, where a remote authenticated user with a low-privileged role can create an administrator account. A separate bulletin the same day covers CVE-2026-126574 in ASUS Control Center Datacenter and Control Center Enterprise, where a remote authenticated user with a Viewer role can change an Administrator account password. We stay with that official wording. We do not link proof-of-concept or exploit code.
Which products and versions are affected, and what is the fixed build?
ASUS's Control Center Express Agent bulletin says the update addresses security vulnerabilities affecting versions earlier than v1.7.29, and tells users to download and install ASUS Control Center Express v1.7.29 or later, then update client agents with Client Agent Updater. Under that bulletin, v1.7.28 counts as affected. The official CVE records for CVE-2026-114202, CVE-2026-114204 and CVE-2026-114205, which apply to Control Center Express only, list the affected versions as through v1.7.27. We follow the bulletin for the upgrade, and we note that CVE wording. ASUS does not name a fixed agent version; run Client Agent Updater and verify the agent version. For Control Center Datacenter and Enterprise, only CVE-2026-126574 applies. The bulletin and that CVE record both list Datacenter 4.0.0.2 and earlier, and Enterprise 3.1.0.8 and earlier, as affected. ASUS does not name an exact fixed build for those editions. It recommends upgrading ASUS Control Center to the latest version.
Can this be used without a signed-in account?
ASUS's Express bulletin and the official CVE records describe CVE-2026-114202 as allowing a remote user to gain administrative privileges via a forged authentication token. Its CVSS 4.0 vector sets Privileges Required to None. We still use ASUS's wording, a remote user. CVE-2026-114204 is different: a remote user can forge a session token for an account with a recent valid login. Its vector sets Attack Requirements to Present and Privileges Required to Low. We do not describe CVE-2026-114204 as needing no login. CVE-2026-114205 is described as a remote authenticated user with a low-privileged role. CVE-2026-126574, which applies only to Control Center Datacenter and Enterprise, is described as a remote authenticated user with a Viewer role.
How do I update Control Center Express?
Vendor advice, from ASUS's Control Center Express Agent bulletin: 1. Download and install ASUS Control Center Express v1.7.29 or later from the official ASUS Control Center Express download page. 2. Select the target devices in the device list. 3. Go to "Select Function" > "Client Agent Updater" to update the client agents. 4. Verify that the agent version shows the updated version. Our advice: patch the console first, then the agents, and do not assume the console upgrade alone has updated every client.
Has this been exploited, and is it in KEV?
None of CVE-2026-114202, CVE-2026-114204, CVE-2026-114205 or CVE-2026-126574 was in CISA's Known Exploited Vulnerabilities catalogue when we checked at 02:32 GMT on 18 November 2026 (catalogue 2026.11.17, released 17:53 GMT on 17 November 2026). The official ASUS bulletins do not give an exploitation status, and no CISA ADP entry was present on the CVE records when we checked. We do not treat absence from KEV as proof that the flaws have been used.
What should we do if we cannot patch immediately?
Our advice, not a workaround from ASUS: keep every Control Center and Control Center Express console off the public internet, on an admin VLAN or reachable only over VPN, until it is patched. Prune low-privileged console accounts you do not need. Because CVE-2026-114202 and CVE-2026-114204 involve a hard-coded cryptographic key, treat any console reachable from an untrusted network as exposed. Still plan the upgrade. After you patch, rotate all console credentials.
Sources and how to get help
- ASUS Security Advisory (18 November 2026 bulletins: Security Update for ASUS Control Center Express Agent, covering CVE-2026-114202, CVE-2026-114204 and CVE-2026-114205; Security Update for ASUS Control Center, covering CVE-2026-126574).
- CVE-2026-114202, CVE-2026-114204, CVE-2026-114205 and CVE-2026-126574 on CVE.org, assigned by ASUS.
- NVD copies, all published 02:17 GMT on 18 November 2026, status Received: CVE-2026-114202, CVE-2026-114204, CVE-2026-114205 and CVE-2026-126574.
- ASUS Control Center Express download page and ASUS Control Center download page.
- ASUS Control Center Express user manual (E24388, version 01.07, revised edition V6, October 2024), including Account Settings (printed page 6-23), which tells users to change the default administrator credentials.
- CISA Known Exploited Vulnerabilities catalogue, checked at 02:32 GMT on 18 November 2026 (catalogue 2026.11.17, released 17:53 GMT on 17 November 2026).
If you want help checking exposure or responding, get in touch with CybaVerse.