CVE-2026-19397

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Missing authentication for a critical function in ASUS Control Center Express Agent allows an unauthenticated nearby user to control the host via a direct connection to the agent when the host has an active login session. Refer to the '  Security Update for ASUS Control Center Express Agent ' section on the ASUS Security Advisory for more information.

CVSS v3
7.7
EG Score
7.7(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity77% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 17, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

ASUS Security Advisory | Latest Vulnerability Update

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

Vendor Advisories for CVE-2026-19397(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 57× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-21 01:27 UTCEG score recompute
  2. 2026-09-21 01:27 UTCGHSA enrichment
  3. 2026-09-20 12:48 UTCGHSA enrichment
  4. 2026-09-20 00:16 UTCEG score recompute
  5. 2026-09-20 00:16 UTCGHSA enrichment
  6. 2026-09-19 11:43 UTCGHSA enrichment
  7. 2026-09-18 23:12 UTCEG score recompute
  8. 2026-09-18 23:11 UTCGHSA enrichment
  9. 2026-09-18 19:27 UTCEPSS rescore
  10. 2026-09-18 10:39 UTCGHSA enrichment
  11. 2026-09-17 22:04 UTCEG score recompute
  12. 2026-09-17 22:04 UTCGHSA enrichment
  13. 2026-09-17 09:32 UTCEG score recompute
  14. 2026-09-17 09:32 UTCGHSA enrichment
  15. 2026-09-17 08:49 UTCEG score recompute
  16. 2026-09-17 08:49 UTCGHSA enrichment
  17. 2026-09-16 22:47 UTCEG score recompute
  18. 2026-09-16 22:47 UTCGHSA enrichment
  19. 2026-09-16 14:07 UTCEPSS rescore
  20. 2026-09-16 10:13 UTCEG score recompute
  21. 2026-09-16 10:13 UTCGHSA enrichment
  22. 2026-09-16 05:14 UTCEPSS rescore
  23. 2026-09-15 21:41 UTCGHSA enrichment
  24. 2026-09-15 09:09 UTCEG score recompute
  25. 2026-09-15 09:09 UTCGHSA enrichment
Show 32 more
  1. 2026-09-14 20:37 UTCGHSA enrichment
  2. 2026-09-14 08:05 UTCGHSA enrichment
  3. 2026-09-13 19:33 UTCEG score recompute
  4. 2026-09-13 19:33 UTCGHSA enrichment
  5. 2026-09-13 16:46 UTCEPSS rescore
  6. 2026-09-13 07:01 UTCGHSA enrichment
  7. 2026-09-12 18:29 UTCEG score recompute
  8. 2026-09-12 18:29 UTCGHSA enrichment
  9. 2026-09-12 15:00 UTCEPSS rescore
  10. 2026-09-12 05:57 UTCGHSA enrichment
  11. 2026-09-11 17:25 UTCEG score recompute
  12. 2026-09-11 17:25 UTCGHSA enrichment
  13. 2026-09-11 14:52 UTCEPSS rescore
  14. 2026-09-11 09:36 UTCEPSS rescore
  15. 2026-09-11 04:50 UTCGHSA enrichment
  16. 2026-09-10 16:18 UTCEG score recompute
  17. 2026-09-10 16:18 UTCGHSA enrichment
  18. 2026-09-10 09:34 UTCEPSS rescore
  19. 2026-09-10 03:46 UTCGHSA enrichment
  20. 2026-09-09 15:14 UTCGHSA enrichment
  21. 2026-09-09 02:42 UTCEG score recompute
  22. 2026-09-09 02:42 UTCGHSA enrichment
  23. 2026-09-08 22:00 UTCEPSS rescore
  24. 2026-09-08 14:09 UTCGHSA enrichment
  25. 2026-09-08 13:42 UTCEG score recompute
  26. 2026-09-08 13:42 UTCGHSA enrichment
  27. 2026-09-08 12:46 UTCEG score recompute
  28. 2026-09-08 12:46 UTCGHSA enrichment
  29. 2026-09-08 03:34 UTCEG score recompute
  30. 2026-09-08 03:34 UTCGHSA enrichment
  31. 2026-09-08 02:30 UTCEG score recompute
  32. 2026-09-08 02:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19397?
CVE-2026-19397 is a high vulnerability published on September 8, 2026. Missing authentication for a critical function in ASUS Control Center Express Agent allows an unauthenticated nearby user to control the host via a direct connection to the agent when the host has an active login session. Refer to the ' Security Update for ASUS Control Center Express Agent '…
When was CVE-2026-19397 disclosed?
CVE-2026-19397 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19397 actively exploited?
CVE-2026-19397 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.2% of all scored CVEs.
What is the CVSS score of CVE-2026-19397?
CVE-2026-19397 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-19397?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19397, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-19397

Explore →

Is Your Infrastructure Affected by CVE-2026-19397?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs