CVE-2026-114205

waiting for further signalsZero needs more public information before it can validate it.

GHSA-8xgj-xrpc-gvj4 ↗EUVD-2026-128399 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
ASUS Control Center Express through v1.7.27
ETK-2026-4982Zero's internal tracking ID, independent of the CVE number., permanent identifier
7h 50msince last run
1h 32mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+46h57m
0
+2h
+4h
+6h
+8h
+10h

description

ASUS Control Center Express has an authorization flaw affecting users with low-privilege authenticated access. Such a user may create an administrator account and gain control of the management console and its managed clients; a valid low-privilege account is required.

mitigation

Apply the current ASUS security update for ASUS Control Center Express. Until patched, restrict access to trusted administrators and review low-privilege accounts and newly created administrator accounts.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 32m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 02:02Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-18 02:02Z
  2. 2026-11-18 02:02Z
  3. 2026-11-19 21:15Z

this entry in the feed

GET /api/v1/feed/CVE-2026-114205

{
  "etk_id": "ETK-2026-4982",
  "cve_id": "CVE-2026-114205",
  "display_id": "CVE-2026-114205",
  "ghsa_id": "GHSA-8xgj-xrpc-gvj4",
  "euvd_id": "EUVD-2026-128399",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper authorization in ASUS Control Center Express",
  "summary": "ASUS Control Center Express has an authorization flaw affecting users with low-privilege authenticated access. Such a user may create an administrator account and gain control of the management console and its managed clients; a valid low-privilege account is required.",
  "mitigation": "Apply the current ASUS security update for ASUS Control Center Express. Until patched, restrict access to trusted administrators and review low-privilege accounts and newly created administrator accounts.",
  "vendor": "ASUS",
  "product": "Control Center Express",
  "affected": [
    {
      "affected_notes": [
        "through v1.7.27"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Control Center Express",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.4,
  "cvss_src": "other",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 92.48878138333333,
  "t0_at": "2026-11-18T02:02:15.149000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T02:02:15.149000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T02:02:15.149000+00:00",
      "url": "https://www.bleepingcomputer.com/news/security/asus-warns-of-critical-hard-coded-key-flaw-in-control-center-express/"
    }
  }
}

published 2026-11-19 23:26Z
last change 2026-11-20 05:08Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.