ASUS says Control Center Express flaws, one scored 10.0, hit versions before 1.7.29; its CVE records stop at 1.7.27
ASUS's bulletin says three Control Center Express flaws, scored 10.0, 9.0 and 9.4, affect versions earlier than v1.7.29, while its CVE records stop at v1.7.27. Read on 20 November 2026: what each page says about v1.7.28, authentication and reach, and what it leaves out.
By Parminder Kumar Sharma · LinkedIn · · 20 min read
ASUS's bulletin says versions earlier than 1.7.29; its three CVE records say through 1.7.27
On 18 November 2026 ASUS, acting as the assigner, published three CVE records for ASUS Control Center Express between 02:01 and 02:02 UTC, and a security bulletin titled "Security Update for ASUS Control Center Express Agent". The records score the three flaws 10, 9 and 9.4 on CVSS 4.0. Each record lists the affected versions as "through v1.7.27". The bulletin says the update "addresses security vulnerabilities affecting versions earlier than v1.7.29", and the advisory list row says "affecting versions prior to v1.7.29". That is the checkable fact: one fix version, three wordings, and a gap between the first two. Between "through v1.7.27" and "earlier than v1.7.29" the only patch number is v1.7.28 (derived: 29 minus 27 leaves one number, if releases are numbered one by one, which no saved page says). The bulletin covers it. The records do not list it.
The bulletin says that, if exploited, the issues "could allow a remote user to bypass authentication or improperly gain administrator-level access to the management console and the clients it manages". Control Center Express is described by BleepingComputer, a secondary, as a central dashboard for managing fleets of PCs; the records and the bulletin themselves say "the management console and the clients it manages". An administrator token on such a console is not only the console's problem, but how far it reaches is not on the saved pages. Here is what the pages do not establish:
- Whether v1.7.28 exists, and whether it is affected. No saved page prints "v1.7.28" except BleepingComputer, which calls its status unclear.
- Whether anyone has exploited any of the flaws. No saved page reports exploitation. Inside each CVE record a CISA container prints an exploitation rating of none, stamped at a time shown below; this site saved no catalogue file and makes no claim about any catalogue.
- How many installations exist, how many clients a console manages, or whether consoles are reachable from the internet. No saved page says.
- Whether the hard coded key is the same in every installation. The records say a key is hard coded. They do not say it is shared. This site does not assume it.
- How the flaws were found. The records carry credit entries; this site names no individual and prints none.
- The fix status of the Control Center Enterprise and Datacenter record, and of the earlier record CVE-2026-75754. The saved pages print affected versions only.
Three wordings for the affected versions, and the one number between them
Diagram 1 puts the three wordings on one axis. The bands are version slots, not a time scale, and only three version numbers appear on any saved ASUS page: v1.7.27 in the records, v1.7.29 in the bulletin and the list row, and nowhere v1.7.28.
Table 1. How each saved page words the affected versions of Control Center Express.
| Page | What it prints | What follows |
|---|---|---|
| CVE-2026-114202, 114204 and 114205 (ASUS as assigner) | "through v1.7.27", with defaultStatus "unaffected" | v1.7.28 is outside the listed range. The record format applies defaultStatus to versions not listed, so read literally the records put v1.7.28 outside the affected range (this site's reading of the field) |
| ASUS bulletin, Security Update for ASUS Control Center Express Agent | "affecting versions earlier than v1.7.29" | v1.7.28, if it exists, is affected. The fix is "v1.7.29 or later" |
| ASUS advisory list row for the same three CVE ids | "affecting versions prior to v1.7.29" | The same coverage as the bulletin in different words |
| BleepingComputer, 19 November 2026 (secondary) | The records "only list affected versions through v1.7.27, leaving the status of v1.7.28 unclear" | It reports the mismatch; it does not say whether v1.7.28 exists |
The records and the bulletin were published by the same company on the same day, so the difference is ASUS's own. This site does not resolve it. Which of the two a reader should follow on v1.7.28 is a choice the reader has to make, and the cautious reading is the bulletin's, which asks for v1.7.29 or later (this site's reading). The bulletin says ASUS "strongly recommends that users update their installation immediately".
Three flaws, scored 10, 9 and 9.4, and what each page says about who can use them
The records name the flaws plainly. CVE-2026-114202 and CVE-2026-114204 are the same weakness, "Use of Hard-coded Cryptographic Key" (CWE-321). The first, the record says, "allows a remote user to gain administrative privileges via a forged authentication token". The second lets a remote user "bypass authentication by forging a session token for an account with a recent valid login", which the record says results in "administrative control of the management console and of the clients it manages". CVE-2026-114205 is "Incorrect Authorization" (CWE-863): it "allows a remote authenticated user with a low-privileged role to create an administrator account", with the same console and clients result.
Table 2. The three Control Center Express records as saved on 20 November 2026. All three were published on 18 November 2026 and list the affected versions as "through v1.7.27".
| CVE | Weakness as the record names it | Who, in the record text | CVSS 4.0 score in the record |
|---|---|---|---|
| CVE-2026-114202 | CWE-321 Use of Hard-coded Cryptographic Key | a remote user | 10 (CRITICAL) |
| CVE-2026-114204 | CWE-321 Use of Hard-coded Cryptographic Key | a remote user, for an account with a recent valid login | 9 (CRITICAL) |
| CVE-2026-114205 | CWE-863 Incorrect Authorization | a remote authenticated user with a low-privileged role | 9.4 (CRITICAL) |
Diagram 2 sets the weakness, the vector letters, the score and each page's words about authentication side by side. Dashed cells are where a page prints nothing on the point.
Three statements about authentication differ, and all three are printed:
- For CVE-2026-114202, BleepingComputer says the flaw lets "an unauthenticated remote attacker forge an authentication token", "without requiring any privileges or user interaction". The record text says only "a remote user". The vector the bulletin prints and the record carries has PR:N (privileges required: none) and UI:N (user interaction: none), which agrees with the secondary. CISA's container in the record rates it Automatable: yes.
- For CVE-2026-114204, the vector prints PR:L (privileges required: low) and AT:P (attack requirements: present). The record text names no privilege level; it names "an account with a recent valid login". BleepingComputer says "a remote attacker with low privileges" and that the flaw has "a recent-session prerequisite". The saved pages do not say whose login must be recent, or how recent.
- For CVE-2026-114205, the record says "remote authenticated" and "a low-privileged role", and the vector prints PR:L, which agrees.
The three vectors share AV:N, AC:L, UI:N and a high (H) value on all six impact letters (VC, VI, VA, SC, SI, SA). They differ in AT and PR only. CVE-2026-114202 and CVE-2026-114205 differ in exactly one letter, PR, and the score falls by 0.6 (derived: 10 minus 9.4). CVE-2026-114204 differs from CVE-2026-114202 in two letters, AT and PR, and the score falls by 1 (derived: 10 minus 9). The full decoding is in the technical section below.
What a console token reaches, and what the pages leave out
The bulletin says the issues could let a remote user "improperly gain administrator-level access to the management console and the clients it manages". The records for CVE-2026-114204 and CVE-2026-114205 repeat "the management console and of the clients it manages". The record for CVE-2026-114202 says "administrative privileges" and does not mention clients. So the reach on the page is this: the console, and the machines it manages. An administrator of a console can act on every client it manages (this site's reading of "manages"), which is why the first line of defence is who can reach the console, and why the second is the version of the console and of every client agent.
Here is what the saved pages leave out. They give no count of installations and no count of clients per console. They do not say whether a console is normally reachable from the internet or only from an office network. They do not say what an administrator can do to a client, beyond "administrator-level access". BleepingComputer, a secondary, says ASUS markets the product to businesses and IT service providers and lists support for "more than 200" business, workstation and Corporate Stable Model motherboards. Neither the bulletin nor the records say either of those things, so both statements rest on the secondary alone.
Two labels do the work of a control here and are not one. The bulletin is titled "Security Update for ASUS Control Center Express Agent", and the records tell the reader to refer to that section. Yet the bulletin's own text speaks of a "Software Update for ASUS Control Center Express", asks the reader to install v1.7.29 of the console, and only then to use "Client Agent Updater" on the managed devices. A reader who searches an inventory for "Agent" may find the second stage and miss the first. And "Critical" is a label on a score, not a statement about whether anyone has attacked: the records print it for all three flaws, and nothing on the saved pages says what is happening outside the vendor.
The line of Control Center records: five records in 75 days across four name strings
This is the line the Express records sit on. The earliest is CVE-2026-75754, published on 4 September 2026 and scored 10; the other four were published on 18 November 2026 within 50 seconds (derived: 02:01:45 to 02:02:35 UTC). From 4 September to 18 November is 75 days (derived: 26 days left in September, 31 in October, 18 in November). Diagram 3 draws the five on one time axis.
Table 3. The five Control Center records, with the product names and versions exactly as each record prints them.
| CVE | Published (UTC) | Product and versions as printed | Score and weakness |
|---|---|---|---|
| CVE-2026-75754 | 4 Sep 2026, 02:08 | Control Center Enterprise (ACC), through 4.0.0.2 | 10; CWE-306, CWE-918, CWE-798 |
| CVE-2026-114204 | 18 Nov 2026, 02:01 | Control Center Express, through v1.7.27 | 9; CWE-321 |
| CVE-2026-114205 | 18 Nov 2026, 02:02 | Control Center Express, through v1.7.27 | 9.4; CWE-863 |
| CVE-2026-114202 | 18 Nov 2026, 02:02 | Control Center Express, through v1.7.27 | 10; CWE-321 |
| CVE-2026-126574 | 18 Nov 2026, 02:02 | Control Center Datacenter, 4.0.0.2 and earlier; Control Center Enterprise, 3.1.0.8 and earlier | 9.4; CWE-862 |
The records print four different product strings: "Control Center Express", "Control Center Enterprise (ACC)", "Control Center Datacenter" and "Control Center Enterprise". Counting the ACC string as Enterprise gives three products (this site's reading; no saved page says the two are one product). Two version series also overlap without explanation: the earlier record says Control Center Enterprise (ACC) through 4.0.0.2, while the newer record says Control Center Datacenter 4.0.0.2 and earlier and Control Center Enterprise 3.1.0.8 and earlier. The saved pages do not reconcile them.
CVE-2026-126574 is the sibling to read: a missing authorization flaw (CWE-862) in which, the record says, a remote authenticated user "with a low-privileged Viewer role" can change the password of an Administrator account and so obtain administrative privileges. It carries the same score and vector as CVE-2026-114205 (9.4). The advisory list row, "Security Update for ASUS Control Center", prints the affected versions and the CVE id and nothing else about a fix; BleepingComputer says ASUS "patched" it. This site cannot give a fixed version for it from the saved pages.
CVE-2026-75754 is context. Its record lists three weaknesses, missing authentication for a critical function, server side request forgery and hard coded credentials, and scores 10. It says the result is "remote control of all servers, PCs, and workstations within the company". That is the vendor's own description of reach for that product and it is a different product string from Express. The record prints no fixed version and says to refer to the "Security Update for ASUS Control Center" section; it was last updated on 17 September 2026. This site prints none of the technique the record describes. The saved pages do not say whether it was fixed, or in which version.
One more small figure: for the three Express records the id was reserved on 21 October and the records were published on 18 November, 28 days later (derived). A reservation date is a record-keeping step; the saved pages do not say when ASUS received any report.
What CISA's container inside each record prints
Each saved CVE record carries a second container from CISA ("CISA ADP Vulnrichment", role "CISA Coordinator") with three options. They are CISA's wording, rated at the time stamped. This site saved no catalogue file, so it says nothing about any catalogue entry in either direction.
Table 4. The CISA-ADP options inside each saved record, with the time of the rating (UTC, to the minute).
| Record | Exploitation | Automatable | Technical Impact | Rated at |
|---|---|---|---|---|
| CVE-2026-114202 | none | yes | total | 18 Nov, 19:16 |
| CVE-2026-114204 | none | no | total | 18 Nov, 19:15 |
| CVE-2026-114205 | none | no | total | 19 Nov, 17:02 |
| CVE-2026-126574 | none | no | total | 18 Nov, 19:08 |
| CVE-2026-75754 | none | yes | total | 4 Sep, 19:46 |
Read what this does and does not say. "Exploitation: none" is a rating at the stamp: 18 November for CVE-2026-114202, 114204 and 126574, 19 November for CVE-2026-114205 and 4 September for CVE-2026-75754. It does not say what has happened since, and it is not a statement from ASUS. The two records scored 10, CVE-2026-114202 and CVE-2026-75754, are the two rated Automatable: yes (derived by reading the columns); the 9 and 9.4 records are rated no. All five are rated Technical Impact: total.
Where the pages differ, with nothing resolved
Table 5. Differences between and inside the saved pages. Each is reported as printed; none is resolved.
| Point | One page prints | Another prints |
|---|---|---|
| Affected versions | CVE records: "through v1.7.27" | Bulletin: "earlier than v1.7.29". List row: "prior to v1.7.29" |
| Authentication for CVE-2026-114202 | BleepingComputer: "unauthenticated". Vector PR:N, UI:N | CVE record text: "a remote user". CISA-ADP: Automatable yes |
| Authentication for CVE-2026-114204 | Vector: PR:L and AT:P. BleepingComputer: "low privileges" | CVE record text: "an account with a recent valid login", no privilege level |
| Which CVSS version the score belongs to | All five records carry CVSS 4.0 scores: 10, 9 and 9.4 for the Express records, 9.4 and 10 for the other two | The bulletin prints "CVSS 4.0 Score" 10.0, 9.0 and 9.4 for the three flaws, with the same vectors. All three agree with the records |
| Product names | Express, Enterprise (ACC), Datacenter, Enterprise | List row title: "Security Update for ASUS Control Center" for the Datacenter and Enterprise record |
| Where the flaw is | Records and bulletin text: the management console and the clients it manages | Bulletin title and the records' pointer: "Control Center Express Agent" |
| Secondary statements | BleepingComputer: "more than 200" motherboards; markets it to businesses and IT service providers | Neither statement is on the bulletin or the records |
| Last updated stamps | Bulletin: "Last Updated: November 18, 2026 (GMT+8)", a date and zone with no time. In UTC that day runs from 16:00 on 17 Nov to 15:59 on 18 Nov (derived) | List row: 11/18/2026 for published and last updated, no time or zone. CVE records: published 18 Nov, 02:01 to 02:02 UTC, with their own later update stamps |
The list row prints "11/18/2026" as both the published and the last updated date. This site reads that month first, as 18 November, because the CVE records were published that day and no month numbered 18 exists.
What the pages state, and what they do not
Table 6. What the saved pages establish and what they leave open.
| Question | Stated | Not stated |
|---|---|---|
| Which versions are affected? | Records: through v1.7.27. Bulletin: earlier than v1.7.29. Fix: v1.7.29 or later | Whether v1.7.28 exists or is affected |
| How bad is each flaw? | CVSS 4.0 base scores 10, 9, 9.4, all CRITICAL, with vectors; the bulletin prints the same three | Any real world measure of harm |
| What does an attacker get? | Administrator access to the console and the clients it manages (bulletin and two records) | What administrators can do to a client; how many clients a console manages |
| Is it exploited? | CISA-ADP rated Exploitation none at the stamps in Table 4 | Anything since those stamps; any catalogue entry (none saved) |
| Is it reachable from the internet? | The vector prints AV:N, network | How many consoles are exposed; the usual deployment |
| Is the hard coded key shared? | CWE-321, a hard-coded cryptographic key, in two records | Whether the key is the same in every installation |
| How were they found? | Each record has a credit entry | This site prints no name |
| What about Enterprise and Datacenter? | A list row and a record for CVE-2026-126574 with affected versions | A fixed version; whether CVE-2026-75754 was fixed |
The versions, vectors and update steps, as the records and the bulletin print them
This section is defensive only. The saved pages print no token format, no key value, no request and no exploit steps, and this site prints none. They print no indicators of compromise and no reports of exploitation. What they print is below, copied as printed, so that a defender can check versions and follow the vendor's update path.
Table 7. Per flaw: weakness, versions and fix as the saved pages print them (CVE records and ASUS bulletin, read 20 November 2026).
| Field | CVE-2026-114202 | CVE-2026-114204 | CVE-2026-114205 |
|---|---|---|---|
| Weakness (record) | CWE-321 Use of Hard-coded Cryptographic Key | CWE-321 Use of Hard-coded Cryptographic Key | CWE-863 Incorrect Authorization |
| Affected (record) | Control Center Express, through v1.7.27 | Control Center Express, through v1.7.27 | Control Center Express, through v1.7.27 |
| Affected (bulletin) | earlier than v1.7.29 | earlier than v1.7.29 | earlier than v1.7.29 |
| Fix (bulletin) | v1.7.29 or later | v1.7.29 or later | v1.7.29 or later |
| CVSS 4.0 score (bulletin; record) | 10.0 Critical; 10 | 9.0 Critical; 9 | 9.4 Critical; 9.4 |
| Published (UTC) | 18 Nov 2026, 02:02 | 18 Nov 2026, 02:01 | 18 Nov 2026, 02:02 |
| Record last updated (UTC) | 18 Nov 2026, 19:16 | 18 Nov 2026, 19:15 | 19 Nov 2026, 17:02 |
Table 8 decodes each metric from the letters the vector prints and the words the record prints for the same metric. The prefix of every vector is "CVSS:4.0".
Table 8. The three vectors, metric by metric (letters as printed; words as the CVE records print them).
| Metric | CVE-2026-114202 | CVE-2026-114204 | CVE-2026-114205 |
|---|---|---|---|
| AV (attackVector) | N, NETWORK | N, NETWORK | N, NETWORK |
| AC (attackComplexity) | L, LOW | L, LOW | L, LOW |
| AT (attackRequirements) | N, NONE | P, PRESENT | N, NONE |
| PR (privilegesRequired) | N, NONE | L, LOW | L, LOW |
| UI (userInteraction) | N, NONE | N, NONE | N, NONE |
| VC, VI, VA (vulnerable system impact) | H, H, H: HIGH, HIGH, HIGH | H, H, H: HIGH, HIGH, HIGH | H, H, H: HIGH, HIGH, HIGH |
| SC, SI, SA (sub fields; this site reads them as systems beyond the vulnerable one) | H, H, H: HIGH, HIGH, HIGH | H, H, H: HIGH, HIGH, HIGH | H, H, H: HIGH, HIGH, HIGH |
| Base score, severity | 10, CRITICAL | 9, CRITICAL | 9.4, CRITICAL |
In plain words, read from those letters: all three are reachable over the network (AV:N) with low attack complexity (AC:L) and no user interaction (UI:N). CVE-2026-114202 needs no privileges (PR:N) and no attack requirements (AT:N). CVE-2026-114204 needs low privileges (PR:L) and has attack requirements present (AT:P), which the record text ties to an account with a recent valid login. CVE-2026-114205 needs low privileges (PR:L) and no attack requirements (AT:N). All three print high impact on the vulnerable system and on the sub fields.
The first block is the vendor's update path, copied from the bulletin. It has two stages: the console, then the client agents.
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.
The second block is what the bulletin and the records print as scores and vectors. The three agree letter for letter. The bulletin's Last Updated line is a date with a GMT+8 zone and no time.
From the bulletin (printed without the CVSS:4.0 prefix):
CVE-2026-114202 CVSS 4.0 Score 10.0 / Critical
AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CVE-2026-114204 CVSS 4.0 Score 9.0 / Critical
AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CVE-2026-114205 CVSS 4.0 Score 9.4 / Critical
AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Last Updated: November 18, 2026 (GMT+8)
From the CVE records (vectorString):
CVE-2026-114202 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CVE-2026-114204 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CVE-2026-114205 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
The third block is CISA's rating inside each record. The options are CISA's wording; each is a rating at its stamp.
CVE-2026-114202 CISA-ADP, role CISA Coordinator, SSVC 2.0.3, timestamp 2026-11-18T19:16:37Z: Exploitation none, Automatable yes, Technical Impact total
CVE-2026-114204 CISA-ADP, role CISA Coordinator, SSVC 2.0.3, timestamp 2026-11-18T19:15:04Z: Exploitation none, Automatable no, Technical Impact total
CVE-2026-114205 CISA-ADP, role CISA Coordinator, SSVC 2.0.3, timestamp 2026-11-19T17:02:17Z: Exploitation none, Automatable no, Technical Impact total
CVE-2026-126574 CISA-ADP, role CISA Coordinator, SSVC 2.0.3, timestamp 2026-11-18T19:08:48Z: Exploitation none, Automatable no, Technical Impact total
CVE-2026-75754 CISA-ADP, role CISA Coordinator, SSVC 2.0.3, timestamp 2026-09-04T19:46:22Z: Exploitation none, Automatable yes, Technical Impact total
Table 9. The two sibling records as printed.
| Field | CVE-2026-126574 | CVE-2026-75754 |
|---|---|---|
| Product and versions | Control Center Datacenter 4.0.0.2 and earlier; Control Center Enterprise 3.1.0.8 and earlier | Control Center Enterprise (ACC), through 4.0.0.2 |
| Weakness | CWE-862 Missing Authorization | CWE-306, CWE-918, CWE-798 |
| Score (CVSS 4.0) | 9.4, CRITICAL, PR:L | 10, CRITICAL, PR:N |
| Published and last updated | 18 Nov 2026; 18 Nov 2026 | 4 Sep 2026; 17 Sep 2026 |
| Fixed version | Not printed in the saved pages | Not printed in the saved pages |
What to do, in order
First, what ASUS says: update immediately, to v1.7.29 or later, then update the client agents and check their versions. The rest is this site's suggestion, and it is written knowing the saved pages do not say how a given console is reached or run.
Take this with you
A checklist for anyone who runs an ASUS Control Center product
- Find every Control Center installation: Express, Enterprise and Datacenter, including any run for you by a service provider (this site's suggestion).
- ASUS: download and install ASUS Control Center Express v1.7.29 or later, select the target devices, go to Select Function and Client Agent Updater to update the client agents, and verify that each agent shows the updated version.
- If you run v1.7.28, do not assume safety. The CVE records stop at v1.7.27; the bulletin says earlier than v1.7.29 (this site's reading: follow the bulletin).
- Restrict who can reach the console. Do not expose it to the internet. The saved pages do not say whether consoles are normally reachable from outside, so check yours (this site's suggestion).
- Review the administrator accounts on the console, and the recent logins, for any you do not recognise (this site's suggestion).
- Enterprise and Datacenter users: read the ASUS bulletin for CVE-2026-126574 and apply the vendor fix. The saved list row prints affected versions only: Datacenter 4.0.0.2 and earlier, Enterprise 3.1.0.8 and earlier.
- After patching, rotate administrator credentials and end open sessions. The key is hard coded in the product, so a token forged before the patch may be the concern (this site's suggestion; the saved pages do not say whether any token was forged).
- Do not read "no exploitation reported" as safe. The rating inside the records is a rating at a time, and the vendor says nothing about exploitation (this site's suggestion).
The question the records leave open
If the records say 1.7.27 and the bulletin says before 1.7.29, which version do you trust on 1.7.28, and who in your estate has already decided for you by pasting one of the two into a vulnerability scanner? ASUS can settle it with one line in a record. Until then, a console that manages other computers is being patched against whichever of two wordings the scanner happens to carry.
Key facts
Sources
- PrimaryThe ASUS Product Security Advisory page: the list rows for Control Center Express Agent and Control Center, and the text of the bulletin Security Update for ASUS Control Center Express Agent. Rendered text, complete bulletin panel, saved at 09:09 UTC on 20 November 2026ASUSaccessed 2026-11-20
- PrimaryCVE-2026-114202, use of a hard-coded cryptographic key in Control Center Express: description, affected versions, CVSS 4.0 score 10 and vector, dates, CISA rating. Read in full on 20 November 2026CVE Services (record assigned by ASUS, with a CISA-ADP container)accessed 2026-11-20
- PrimaryCVE-2026-114204, hard-coded key and session token: description, affected versions, CVSS 4.0 score 9 and vector, dates, CISA ratingCVE Services (record assigned by ASUS, with a CISA-ADP container)accessed 2026-11-20
- PrimaryCVE-2026-114205, incorrect authorization: description, affected versions, CVSS 4.0 score 9.4 and vector, dates, CISA ratingCVE Services (record assigned by ASUS, with a CISA-ADP container)accessed 2026-11-20
- PrimaryCVE-2026-126574, missing authorization in Control Center Datacenter and Enterprise: affected versions, score 9.4, datesCVE Services (record assigned by ASUS, with a CISA-ADP container)accessed 2026-11-20
- PrimaryCVE-2026-75754, an earlier score 10 record for Control Center Enterprise (ACC): weaknesses, affected versions, dates. Read for context onlyCVE Services (record assigned by ASUS, with a CISA-ADP container)accessed 2026-11-20
- Reported bySecondary report of 19 November 2026: the version mismatch, the unauthenticated description, the 200 motherboard figure. Used to find the primaries and attributed where quotedBleepingComputeraccessed 2026-11-20


