🔥 CyberForge CVE of the Day #108
🚨 CVE-2026-114202 — ASUS Control Center Express
🎯 The quick hit:
ASUS Control Center Express has a cryptographic trust problem: the CNA says a remote user can gain administrative privileges using a forged authentication token because of a hard-coded cryptographic key. ASUS rates CVE-2026-114202 10.0 Critical under CVSS4.0 and urges an immediate update.
ASUS's update has two stages: install Control Center Express v1.7.29 or later, then select devices, use Select Function > Client Agent Updater and verify their updated agent versions. A console update alone is incomplete.
Preserve the scope difference: CNA through v1.7.27/defaultStatus unaffected; vendor before v1.7.29. Sources do not reconcile 1.7.28; follow the supported 1.7.29-or-later route, not a supposed fixed 1.7.28.
Prioritise applicable reachable management installations and sensitive clients. Inventory, preserve, update main/agents and verify active state. Investigate history separately; severity, KEV absence and quiet logs establish neither compromise nor safety.
🔑 Key details:
• CVE-2026-114202 is PUBLISHED; CNA/vendor ASUS; Control Center Express. Bulletin 3130: Security Update for ASUS Control Center Express Agent. One primary CVE.
• Weakness: CWE-321 — Use of Hard-coded Cryptographic Key, assigned by the ASUS CNA. Finder credit: 0x0dee.
• CNA scope: literal custom version “through v1.7.27”, status affected, defaultStatus unaffected. No lower starting release or numeric lessThan field is supplied. Preserve the raw row, not an invented range.
• Vendor scope/remedy: before v1.7.29; update main software to v1.7.29 or later, then client agents and their version verification. Do not declare the unresolved 1.7.28 fixed.
• ASUS CVSS4.0 Base 10.0 CRITICAL: 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.
• Network/low complexity/no attack requirements/no prior privilege/no interaction are the scoring conditions, not proof of Internet exposure.
• High vulnerable/subsequent impacts do not prove client compromise or OS SYSTEM access.
• NVD: Received; displays an ASUS-orgID Secondary 10.0 metric with the same Base values and appended optional:X fields. No independent NVD rating, CVSS3.1 or CVSS2 score is supplied by the captured primary records.
• KEV: exact non-match in complete catalog 2026.11.18, 1,786 entries, checked 19th November. Not a local safety conclusion.
• FIRST EPSS: 0.006620000 = 0.662%; percentile 0.523760000 = 52.376th percentile; score date 18th November 2026, distinct from retrieval. Forecast/rank, not observed compromise.
🧬 What actually went wrong?
The boundary is untrusted input → token verification → administrative product privileges. ASUS supplies the hard-coded-key weakness and forged-token consequence; algorithm, token format, key, endpoint, port and header were not verified.
No JWT/SAML/cookie or cryptographic primitive is assumed. No key was extracted, token generated or request sent. This is source analysis, not reproduced bypass or validated detection.
Password changes or outer authentication are not proof this trust logic is repaired. Review direct paths and use the vendor correction; customer key replacement or universal token revocation is undocumented.
ASUS's shared bulletin describes management-console and managed-client consequences across three issues. For 114202 alone, retain the CNA's administrative privilege result. Do not import code execution, arbitrary file writes, persistence or a complete fleet compromise from another identifier or from the subsequent-system CVSS metrics.
📦 Which deployments belong in scope?
Inventory actual main installations and every client agent, including old servers, active provenance and offline/failed devices. Stored installers or a current main label do not prove client active state.
Keep the CNA through v1.7.27/defaultStatus and the broader before v1.7.29 bulletin side by side. The 1.7.28 gap remains unresolved. The CNA CPE embeds a custom version phrase; do not use it as a universal lexical comparison rule or invent a backport/lower boundary. Follow ASUS's supported update target and clarify ambiguous installed versions with the vendor.
The October 2024 manual locates main version at Settings > Options > General Configuration and Agent Version in the device list/Device Information. Older UI documentation is not current affected-range or exact-schema proof; confirm the installed release.
Verify actual management/authentication reachability. AV:N does not prove Internet exposure; internal untrusted access can matter. Separate inactive copies from live services. Do not extend scope to all ASUS hardware, routers, Armoury Crate or Enterprise/Datacenter products.
🕰️ Exposure window and timeline:
ASUS CNA publication/provider update: 2026-11-18 02:02:25 CVE metadata/ADP update: 2026-11-18 19:16:50. NVD published 2026-11-18 02:17:39 and modified 2026-11-18 20:18:09; those strings remain as supplied without adding Z, with status Received.
Bulletin 3130 RSS publication is 18th November 10:29:54+0800, or 02:29:54 UTC; API publication is 02:29:54. API update 01:30Z precedes publication for an unknown reason. Preserve both; landing/cache data does not override the readable bulletin.
CISA ADP SSVC at 2026-11-18 19:16:37 says Exploitation:none, Automatable:yes, Technical Impact:total. Those are dated provider categorisations, not continuous proof about present attacks or a working exploit built here. No primary original PoC/writeup or field incident was independently verified in the focused source set; search non-discovery is not proof of absence.
CyberForge evidence cutoff: 2026-11-19 07:50:22. A local hunt window follows supported affected main/client deployment and reachability history, potentially before disclosure, through evidenced correction. Record clocks, retention, cleanup and offline coverage. No local exposure interval or verified corrected-installer release date was established here.
🗺️ MITRE ATT&CK:
Conditional analyst mapping: T1190 — Exploit Public-Facing Application, Enterprise ATT&CK. The direct technique page was checked 19th November2026; no frozen release number is asserted. The behaviour basis is ASUS's network forged-token administrative capability, applied only where an actually public-facing affected installation is exploited.
Pivot from relevant access/context to accepted management actions and independent client outcomes. The technique definition is not a case-specific IOC or proof a local attack occurred. AV:N alone does not establish the public-facing premise; internal-only cases need their own behaviour analysis.
No token format was verified, so no SAML/JWT/cookie-specific forgery sub-technique is invented. A forged token does not prove a legitimate password was stolen or justify automatic Valid Accounts mapping. Client OS execution, persistence, lateral movement and exfiltration need separate supporting behaviour.
Reference: https://attack.mitre.org/techniques/T1190/
🧭 SOC investigation trail:
Objective: establish applicability, explain activity and corroborate outcomes. Name devices, UTC interval, sources, access and collection limits. Proposed work only; public sources reviewed.
C01 — Scope the main system, client agents and reachability
Action: inventory actual main/client versions and management access.
Location: supported main view, device-list Agent Version/Device Information, deployment and access records.
Signal: published affected scope with reachable functionality.
Correlate: server/client identity, owner, update/deployment dates and direct/intermediary routes.
Benign causes/limits: current console or stored installer does not prove all clients updated; offline/stale inventory and the unresolved 1.7.28 gap matter.
Escalate: affected reachability or an unresolved build/path to the service/vendor owner; exposure is not compromise.
C02 — Preserve available management and client context
Action: retain time-bounded existing records before upgrade/cleanup where feasible, subject to urgency.
Location: supported Event Log software CSV, Mission Center results, actual auth/edge/network, endpoint and change evidence.
Signal: original times, device/account/action/result context and provenance where collected.
Correlate: clocks, collector delay, logging/cleanup/retention and offline intervals.
Benign causes/limits: the older manual documents optional login logging and deletable entries, not complete token/admin audit coverage. Restrict tokens/credentials.
Escalate: imminent loss or missing outcomes, recording the coverage gap.
C03 — Hunt unexplained administrative activity
Action: review privileged actions/sessions/jobs that responsible users cannot explain.
Location: available product event/job/audit data and verified edge/network metadata.
Signal: unexpected administrative operation or client-targeted job; a hypothesis, not a signature.
Correlate: actual action/job IDs, owner/device, trusted source attribution, times and approved schedules.
Benign causes/limits: legitimate session reuse, delegation, automation and missing optional logs can explain a missing login chain; app activity need not create a Windows logon.
Escalate: a coherent unexplained sequence on an applicable installation after source-health and owner review.
C04 — Corroborate client outcomes independently
Action: determine what a suspicious operation changed on each target.
Location: actual job/result exports, endpoint process/file/configuration/service, network and approved-change records.
Signal: an unauthorised outcome, beyond a queued task or successful response.
Correlate: stable client identity, verified job IDs, process/context and clocks.
Benign causes/limits: maintenance and legitimate deployments resemble management use; PID reuse, shared proxies and missing endpoint data limit attribution. This CVE alone proves no OS SYSTEM access or fleet compromise.
Escalate: corroborated outcomes to IR with exact device/capability scope.
C05 — Apply the main update and client-agent rollout
Action: obtain supported ASUS v1.7.29-or-later software, update main installation, select devices and use Select Function > Client Agent Updater.
Location: bulletin 3130, official supported release/change evidence, device list and updater results.
Signal: main correction plus the corresponding agent update on every intended client.
Correlate: all main servers/groups, offline/failed devices and normal management health.
Benign causes/limits: installer success or a main label is incomplete; component file versions need vendor mapping. No installer was downloaded/verified here.
Escalate: missing trusted media, failed clients, version ambiguity or service degradation.
C06 — Verify active state and investigate history separately
Action: accept main/client active versions and health, then assign the historical evidence disposition.
Location: supported version views, suitably trusted endpoint/service/process provenance, updater/change and health records.
Signal: every intended active client/main instance matches the chosen corrected release mapping; offline/failed targets remain tracked.
Correlate: update/start times, executable identity, reachability and prior interval.
Benign causes/limits: cached inventory, a new disk file or Running service alone proves no active authentication fix; session/token invalidation behaviour is undocumented here.
Escalate: stale state, continuing activity, failed acceptance or missing evidence to the assigned owner.
Handover: device/owner → interval → record IDs → result/confidence → gaps → next action. Separate applicability, exposure, suspicion, compromise and insufficient telemetry. Negative results need searched scope/health. No findings ≠ proof of a clean system.
🔎 Indicators and observable behaviour:
No verified CVE-specific malicious address, domain, hash, actor infrastructure, token value/pattern or universal log signature was established. ASUS names, administrative labels and token-looking strings are context, not malicious indicators.
Hunt unexplained privileged jobs and independent endpoint changes using verified fields/time. Queued jobs differ from completed actions; HTTP success is not forgery, and Windows logon is not application token acceptance.
Valid sessions, authorised automation/delegation and routine maintenance are competing explanations. Optional login-event logging, cleanup, absent clients and retention gaps weaken negative conclusions. A no-match result cannot clear the deployment or a historical interval without an explicit evidence boundary.
🧰 Optional CVE checks:
Two Windows PowerShell examples are source-checked, not executed or tested against representative data. Confirm compatible Windows/.NET/PowerShell and authorised local access. They inspect one known file/service; they do not authenticate to ASUS, generate tokens or alter agents. Prefer supported UI/exports on other or unsupported platforms.
Check A — one agent executable's version resources. Replace OWNER_CONFIRMED_AGENT_EXE with the actual absolute path verified by the owner; it is not an ASUS default path. Use the authorised local host or approved collected file, read permission and recorded UTC/provenance.
```powershell
[System.Diagnostics.FileVersionInfo]::GetVersionInfo('OWNER_CONFIRMED_AGENT_EXE') |
Select-Object FileName, FileVersion, ProductVersion
```
FileName/FileVersion/ProductVersion are metadata resources. Compare with the chosen supported release's component mapping and Agent Version; strings may differ. Do not infer a fixed build from lexical order or any value above 1.7.27. Missing file, denied access or absent resources means incomplete evidence. This establishes neither signature/integrity, loaded code, all clients nor no compromise.
Reference: https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.fileversioninfo.getversioninfo?view=net-10.0
Check B — one owner-confirmed local service registration/state. Replace OWNER_CONFIRMED_AGENT_SERVICE with the exact service Name, not a guessed display name. Retain quoted filter syntax, use approved CIM access and protect account/path output. No remote fleet session is assumed.
```powershell
Get-CimInstance -ClassName Win32_Service -Filter "Name='OWNER_CONFIRMED_AGENT_SERVICE'" |
Select-Object Name, State, ProcessId, StartName, PathName
```
Correlate Name/State/ProcessId/StartName/PathName to the real installation, version and update/start history. PID may be 0 for a stopped service. PathName may include arguments and is not automatically Q01's executable path. StartName is the configured service account, not attacker identity or established gained privilege.
No match, CIM failure or stale registration is not an unaffected result. Running state does not prove corrected token verification or historical safety. No service was started/stopped/changed. Syntax/schema: https://learn.microsoft.com/en-us/powershell/module/cimcmdlets/get-ciminstance?view=powershell-7.5
https://learn.microsoft.com/en-us/windows/win32/cimwin32prov/win32-service
🩹 Remediation and verification:
1⃣ — Assign main/endpoint owners, confirm versions and actual paths, and restrict unnecessary management reachability through supported controls. Record residual paths; restrictions do not repair the trust flaw.
2⃣ — Preserve available event/job/auth/network/endpoint context before disruptive change where feasible. The older manual documents CSV export, optional login logging and deletable entries. Confirm current retention; do not enable/clean logs to fill a checklist.
3⃣ — Obtain/install supported ASUS Control Center Express v1.7.29 or later through the official current channel. Then select targets and use Select Function > Client Agent Updater. Check each updated agent version and result. Main-system installation alone is incomplete; offline/failed clients require named follow-up and return-to-service acceptance.
4⃣ — Verify the active main/client versions against the selected release/agent mapping, required service/restart completion and normal owner-approved management workflows. A new disk file, cached inventory or Running service alone is insufficient. Corroborate with trusted independent endpoint evidence where suspected compromise makes console data questionable.
5⃣ — Ask ASUS about token/session/key lifecycle when needed; universal revocation/customer key replacement is undocumented. Password reset, logout or restart is not a verified repair. Credential/data/rebuild work follows evidence and its owner.
Download limitation: direct representative ASUS portal retrieval returned HTTP 501; search indexed 1.7.29 while a cached reader showed 1.7.24. No installer, hash/signature or current artifact availability was independently verified. Obtain trusted supported media/integrity guidance at change time; the readable bulletin still establishes the 1.7.29-or-later target.
Completion means main/client running-state acceptance and health, outstanding devices tracked, and a separately bounded investigation disposition. No findings ≠ proof of a clean system.
🧾 Evidence separation:
Vendor/CNA: ASUS identity, CWE-321, exact 10.0 CVSS4.0 model, finder 0x0dee, literal CNA row and broader bulletin scope/update route. Public API/RSS are two ASUS channels, not independent researchers. NVD repeats the ASUS assessment.
Documentation: the older manual supports version/export/logging context, not 2026 scope or complete audit coverage. Microsoft supports syntax, not an ASUS detector.
CyberForge: priority, six evidence questions, conditional mapping and acceptance guidance. Not established: local applicability, verified primary PoC/field campaign, corrective hunk, token format/key, universal session invalidation or client OS compromise. No product command, forged token, login attempt, mitigation, response, recovery or publication ran here.
🔥 CyberForge verdict:
CVE-2026-114202 undermines a management authentication boundary. ASUS's 10.0 assessment and update urgency support prompt action, with actual versions, reachability and client population established by the owner.
Prove the main/client state and relevant reachability; preserve and explain administrative activity; apply the supported main update and agent rollout; verify active versions and normal health. Resolve historical outcomes separately and retain gaps. Do not replace evidence with a score, optional missing login event or catalog absence.
A corrected console is only one milestone: account for the agents, the active trust boundary and the evidence of what happened before the update.
🔗 Sources and further reading:
ASUS bulletin: Security Update for ASUS Control Center Express Agent
https://www.asus.com/security-advisory/
Official full bulletin via RSS/API, selected item 3130:
https://security-advisory-api.asus.com/rss/securityrss.xml
https://security-advisory-api.asus.com/api/v1/security/securities
CVE record:
https://www.cve.org/CVERecord?id=CVE-2026-114202
NVD:
https://nvd.nist.gov/vuln/detail/CVE-2026-114202
ASUS October 2024 manual — older documentation context:
https://dlcdnets.asus.com/pub/ASUS/mb/14Utilities/ASUS_Control_Center_Express_EM_WEB_EN.pdf
CWE-321 definition:
https://cwe.mitre.org/data/definitions/321.html
CISA KEV:
https://www.cisa.gov/known-exploited-vulnerabilities-catalog
FIRST exact dated forecast:
https://api.first.org/data/v1/epss?cve=CVE-2026-114202
FIRST interpretation:
https://www.first.org/epss/faq
Command method/schema links and MITRE T1190 reference are beside the relevant sections above.