ASUS Control Center - Broken Access Control

published 2022-06-20 4y ago modified 2026-06-17 4mo ago also EUVD-2022-31218

cvss: 7.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits: 0; none known

ASUS Control Center API has a broken access control vulnerability. An unauthenticated remote attacker can call privileged API functions to perform partial system operations or cause partial disrupt of service.

Is CVE-2022-26668 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
NVD	2.0	6.4	AV:N/AC:L/Au:N/C:N/I:P/A:P

Affected products

ASUS Control Center

Classification

Weakness

CWE-269 Improper Privilege Management
CWE-863 Incorrect Authorization

References

twcert.org.tw /tw/cp-132-6055-c6500-1.html
third-party-advisory

Sources

CVE List CVE-2022-26668
NVD CVE-2022-26668

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.