Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-75754 – Unauthenticated Root RCE via Hardcoded SSH Credentials – ASUS Control Center Enterp

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-75754 is a critical vulnerability chain in ASUS Control Center Enterprise (ACC) that combines missing authentication for a critical function, a server-side request forgery (SSRF) flaw, and hard-coded credentials. An unauthenticated network attacker can retrieve the system’s encryption key via an HTTP request, which causes a local service to enable SSH on port 2222, and then log in using hard-coded credentials to obtain a root shell. The issue carries the maximum severity score and enables full compromise of the ACC management server and every server, PC, and workstation it manages.

Technical details

  • Root cause: a critical ACC function lacks authentication (CWE-306) and is reachable via a server-side request forgery path (CWE-918), allowing an unauthenticated HTTP request to obtain the system’s encryption key.
  • Trigger condition: an attacker sends a crafted HTTP request to the exposed ACC service; this causes a local service on the host to enable an SSH listener on TCP port 2222.
  • Hard-coded credentials (CWE-798) built into ACC allow the attacker to authenticate to this newly opened SSH service and obtain a root shell.
  • Attack vector: network, no privileges or user interaction required.
  • Impact: complete read/write/delete access to ACC data and remote control over all servers, PCs, and workstations managed by the ACC instance.

Affected software

  • ASUS Control Center Enterprise (ACC): versions 0 through 4.0.0.2 (inclusive)

Severity

  • CVSS v4.0 Base Score: 10.0 (Critical)
  • 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

Mitigation and recommended actions

  • Immediate: Check the "Security Update for ASUS Control Center" section of the official ASUS Security Advisory for the patched build and upgrade ASUS Control Center Enterprise beyond version 4.0.0.2 as soon as a fix is released.
  • If no patch is yet available for your deployment: remove ACC management interfaces and the associated encryption-key-retrieval endpoint from direct internet/network exposure; restrict access to trusted management networks only via firewall/ACL; block or monitor outbound/inbound traffic to TCP port 2222; audit for unexpected SSH listeners on management hosts; rotate any credentials that may be reachable from ACC-managed hosts.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: ASUS Control Center

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge