What changed
The key behind an authentication token was not a secret
ASUS published fixes for three Control Center Express flaws on 18 November. The sharpest is CVE-2026-114202: a hard-coded cryptographic key can let a remote user forge an authentication token and gain administrative privileges. Two related flaws, CVE-2026-114204 and CVE-2026-114205, have different prerequisites involving a recent valid login or an existing lower-privileged user.
ASUS says versions before 1.7.29 are affected. The CVE record for CVE-2026-114202 lists affected versions only through 1.7.27, so it leaves 1.7.28 unclear. Follow the vendor's release guidance and target 1.7.29 rather than treating the narrower CVE range as proof that 1.7.28 is safe.
Check both sides of the deployment
Defender workflow
Review the console as an access path to the fleet
- 1
Find and update. Inventory Control Center Express installations and versions. Install 1.7.29 and use ASUS's agent updater for managed clients.
- 2
Check who had reachability. Review whether the console was accessible from untrusted networks or broad internal segments. Reduce access to the administrators and management paths that need it.
- 3
Inspect management actions. Examine recent administrator sessions, account changes and commands sent to managed devices. A token-forgery issue makes the provenance of apparently valid sessions worth examining.
Defender note
The console is the starting point, not the end of scope
If someone obtained administrator control of the dashboard, the investigation should include what it could do to client machines. Compare console activity with endpoint events before deciding that a suspicious login was contained to the management host. ASUS has not stated that these flaws are being exploited in the wild.