Skip to content
eastbaycyber

CVE-2026-114202: ASUS Control Center Express Flaw

CVSS · Critical
10.0
In CISA KEV
No
Published
Nov 18
Patch SLA & TriageVector: Network
24 to 48 hours

Critical CVSS (10.0) reachable over network.

Exposure:
Control:
CVSS v3.1 Blast RadiusScore: 10.0
Decode Vector & Sub-Scores →
CVE explainers 10 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-18
▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-114202 is a CVSS 10.0 flaw involving a hard-coded cryptographic key and forged authentication tokens. - ASUS Control Center Express Agent deployments may be exposed; affected and fixed versions are not specified in retrieved sources. - No public proof of concept or confirmed active exploitation was identified, but administrators should restrict management access and obtain ASUS’s security update.

Summary

CVE-2026-114202 affects ASUS Control Center Express, specifically the ASUS Control Center Express Agent referenced by the vendor advisory. The vulnerability is classified as the use of a hard-coded cryptographic key. According to the NVD description, a remote user may gain administrative privileges by presenting a forged authentication token accepted by the affected application.

For context on vulnerability tracking, see our CVE-2026-106126 analysis and CVE-2026-10789 coverage.

Field Value
CVE ID CVE-2026-114202
CVSS base score 10.0
CVSS vector Not exposed in the retrieved NVD record
Attack vector Remote, based on the NVD impact description; exact vector details are not published in the retrieved record
Authentication required Unknown
Privileges required Unknown in the published vector; impact is administrative-privilege gain
Product ASUS Control Center Express / ASUS Control Center Express Agent
Patch available ASUS identifies a security update, but the fixed version was not exposed in the retrieved sources
CISA KEV status Not listed as of the lookup performed on 2026-11-18
Public PoC None identified in the searches performed

The CVE was published on November 18, 2026. Its severity is driven by the potential combination of remote access, authentication bypass through token forgery, and administrative control. A CVSS score of 10.0 should prompt immediate exposure review, even though important implementation details, including the precise CVSS vector and fixed release, remain unavailable.

Missing version data does not show that installations are safe. The available records identify the product but do not state an affected version range. Administrators need to inventory installed agents and compare them with the definitive ASUS bulletin before declaring a deployment remediated.

AnalystImpact · assess the risk

Root Cause

The root cause is a hard-coded cryptographic key used in the ASUS Control Center Express authentication process. Cryptographic keys embedded in software can often be extracted, recovered through reverse engineering, or reused by anyone who obtains the relevant application files. If the service trusts tokens signed or protected with that key, an attacker may be able to generate tokens that appear legitimate.

The NVD description states that the flaw permits a remote user to gain administrative privileges through a forged authentication token. A likely attack sequence is to obtain or derive the embedded key, construct a valid-looking token, submit it to an exposed service, and invoke administrative functionality. The available sources do not identify the token format, endpoint, cryptographic algorithm, key location, or required network path, so those details should not be treated as confirmed facts.

The central security failure is trust in a secret that is not actually secret. Replacing a shared hard-coded key with securely managed, per-installation or per-instance credentials is generally required to prevent one recovered key from enabling token forgery across multiple deployments. Only ASUS can confirm the precise implementation and remediation design.

The practical impact is an authentication-integrity failure rather than merely a local information-disclosure issue. If an attacker can reach the affected service and successfully forge a token, normal credential checks may no longer protect administrative functions. Treat unexplained administrative activity as a potential compromise until logs and system state have been reviewed.

Analyst’s Take: Exposure review should come before assumptions about exploitability. The score is 10.0, but the missing CVSS vector, affected range, and fixed version mean administrators must verify deployment details directly with ASUS while restricting access to the service.

Who Is Exposed?

The identified product is ASUS Control Center Express, with ASUS referring to the affected component as the ASUS Control Center Express Agent. The retrieved NVD record does not provide an affected version range, and the accessible ASUS advisory content did not expose a fixed version number or detailed version table.

Deployment detail Status
ASUS Control Center Express Identified as affected product
ASUS Control Center Express Agent Specifically referenced by ASUS
Affected version range Not specified in retrieved sources
First affected version Unknown
Fixed version Not specified in retrieved sources
Unaffected version Unknown
Internet-exposed management service Higher-priority exposure for review
Internal-only deployment Still potentially exposed to compromised internal hosts or VPN users

Administrators should inventory both the management server and managed endpoints. Product names may appear differently in software inventories, endpoint-management platforms, Windows installed-program listings, service names, or ASUS deployment packages. Record the installed agent version, management-server version, listening interfaces, and network paths used by administrators and endpoints.

Until ASUS publishes or confirms the precise affected and fixed ranges, assume that installed versions covered by the advisory may be vulnerable. Do not mark a system as remediated solely because it has been upgraded to the newest version currently visible in an internal software repository. Verify the package against ASUS’s “Security Update for ASUS Control Center Express Agent” bulletin.

Severity Breakdown

NVD rates CVE-2026-114202 at CVSS 10.0, the critical maximum. The retrieved NVD record did not expose the complete CVSS vector, so the individual component values cannot be stated reliably. The available evidence does not confirm the exact values for attack complexity, privileges required, user interaction, scope, confidentiality impact, integrity impact, or availability impact.

The published impact description explains why the issue is critical. A remote user may forge an authentication token and gain administrative privileges. That implies a potentially severe loss of authorization integrity and administrative control. Depending on the functions available to an administrator, successful exploitation could enable configuration changes, deployment actions, access to managed systems, or disruption of management operations.

CVSS-related element Available assessment
Base score 10.0
Vector string Not exposed in retrieved NVD record
Remote exploitation Described as possible by a remote user
Authentication prerequisite Unknown
Privileges prerequisite Unknown
User interaction Unknown
Confidentiality impact Not separately specified
Integrity impact Administrative privilege gain indicates potentially high impact
Availability impact Not specified
Scope Unknown

Defenders should use the 10.0 rating for prioritization but avoid inventing a vector or assuming that every installation is reachable from the internet. Exposure depends on deployment architecture, firewall policy, management-service binding, VPN access, and segmentation. A system isolated from untrusted networks has a smaller attack surface, but it remains at risk from compromised internal hosts or accounts with network access.

Exploitation Status

CVE-2026-114202 was not listed in the CISA Known Exploited Vulnerabilities catalog as of the lookup performed on November 18, 2026. There is therefore no CISA catalog confirmation that the vulnerability is being exploited in the wild, and no KEV due date or required action applies.

No public proof-of-concept repository or exploit was identified in the searches performed for this assessment. The available primary-source information also does not confirm active exploitation. The current assessment is: public PoC not identified; in-the-wild exploitation not confirmed.

These statements are time-bound and do not show that exploitation is impossible. A vulnerability involving a hard-coded cryptographic key may attract attackers if the affected service is widely deployed or externally reachable. The absence of a KEV entry can reflect a lack of confirmed reporting, a delay in catalog updates, or limited visibility rather than an absence of attacker interest.

Security teams should continue monitoring ASUS advisories, NVD updates, CISA notifications, vendor support channels, threat-intelligence feeds, and internal telemetry. Investigate any unexpected administrative token acceptance, new privileged account, configuration change, or management action regardless of whether a public exploit has appeared.

Sources

The primary technical record is the NVD entry for CVE-2026-114202:

The vendor’s security advisory landing page is the authoritative location for ASUS remediation details. Administrators should consult the bulletin section titled “Security Update for ASUS Control Center Express Agent” for the definitive affected range, fixed version, package, and installation instructions:

CISA’s catalog is relevant for exploitation-status tracking. CVE-2026-114202 was not present in the catalog as of the lookup used for this article:

The retrieved sources do not provide a public PoC, confirmed in-the-wild exploitation, precise CVSS vector, affected version range, or fixed version. Resolve those gaps by checking the live ASUS bulletin and updated NVD data before closing remediation tickets.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

ResponderRunbook · act now

Detection Guidance

Detection should focus on authentication anomalies, administrative actions, unexpected management traffic, and changes to the ASUS Control Center Express installation. The available sources do not document exact log locations, event IDs, endpoint paths, token formats, or vendor-specific alert signatures. Defenders should first identify where the agent and management server record authentication and administrative activity, then baseline normal administrator source addresses and action patterns.

Prioritize events involving successful administrative authentication from unusual hosts, repeated token-validation failures followed by success, privilege changes, administrative actions outside maintenance windows, and connections to management interfaces from untrusted networks. Review both the management server and managed endpoints because a forged token may be accepted by one component while resulting administrative activity appears elsewhere.

A generic SIEM query can help identify suspicious authentication and privilege activity. Field names will vary by product and may require adaptation:

(
  product:"ASUS Control Center Express"
  OR service:"ASUS Control Center Express Agent"
)
AND
(
  event.action:(login OR authentication OR token_validation OR privilege_change)
  OR message:(*token* OR *administrator* OR *admin*)
)
AND
(
  event.outcome:success
  OR outcome:success
  OR message:(*forged* OR *invalid signature* OR *validation failed*)
)

For environments using Windows event collection, begin with a broad search for service and process activity associated with the product, then correlate it with network connections and account changes:

Get-WinEvent -LogName System,Application,Security -MaxEvents 5000 |
  Where-Object {
    $_.Message -match '(?i)ASUS|Control Center Express|Agent|token|administrator'
  } |
  Select-Object TimeCreated, LogName, Id, ProviderName, Message

This is not a confirmed CVE-specific signature. It is an investigation starting point because the vendor’s exact event schema and vulnerable request pattern were not provided in the retrieved sources. Network teams should also review inbound connections to the management service, especially from internet-facing addresses, unapproved administrative subnets, or hosts that do not normally administer ASUS systems.

Remediation Steps

ASUS points administrators to the “Security Update for ASUS Control Center Express Agent” section of its security advisory. The retrieved advisory content does not state the affected version range or fixed version. No specific safe version number can therefore be quoted without risking an inaccurate remediation claim.

The immediate remediation sequence is:

  1. Inventory ASUS Control Center Express Agent and management-server versions.
  2. Obtain the CVE-2026-114202 update directly from ASUS or an authorized enterprise software channel.
  3. Confirm the package’s version and applicability against the full ASUS bulletin.
  4. Test the update in a representative environment.
  5. Deploy it to all affected agents and management components.
  6. Validate that the installed version matches ASUS’s fixed release.
  7. Review logs for suspicious activity before and after deployment.
  8. Rotate relevant administrative credentials if compromise is suspected.

Because the fixed version is currently unspecified in the retrieved sources, do not use an arbitrary version as a remediation target. The operational command depends on the package format and ASUS distribution method. For example, if ASUS supplies an MSI package, an administrator might use a command of this form after verifying the package through the vendor bulletin:

msiexec.exe /i .\ASUS-Control-Center-Express-Agent-FIXED-VERSION.msi /qn /norestart /l*v C:\Windows\Temp\asus-cve-2026-114202.log

FIXED-VERSION is a placeholder and must be replaced with the exact ASUS-provided package name. Do not execute this command with an unverified file or assume that MSI is the vendor’s actual distribution format.

Until the update is confirmed and deployed, apply compensating controls. Restrict the management service to trusted administrator networks, VPN ranges, or dedicated management VLANs. Remove direct internet exposure, enforce firewall allowlists, and limit access from workstation networks. If the product supports disabling unused remote-administration functions, apply that control only after confirming the operational impact with ASUS documentation.

Example firewall policy logic is shown below; adapt ports and service identifiers to the actual deployment rather than copying unverified port values:

Allow: approved-management-vlan -> ASUS Control Center Express service
Allow: approved-admin-vpn -> ASUS Control Center Express service
Deny: internet -> ASUS Control Center Express service
Deny: general-user-networks -> ASUS Control Center Express service
Log: all denied connection attempts to the service

If unauthorized administrative activity is found, isolate the affected management server, preserve logs and system images according to incident-response procedures, rotate relevant credentials, review managed endpoints for follow-on changes, and contact ASUS support. Patching alone does not establish that an attacker did not already use the vulnerability.

Last verified: 2026-11-18

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.