CVE-2026-16727

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
7.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.3Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (ASUSTeK Computer Incorporation) lists ASUS Armoury Crate versions V5.4.1 up to and including V6.4.12 as affected. No release containing a fix is confirmed on record.

Concurrent Execution using Shared Resource with Improper Synchronization (“Race Condition”) in ASUS Armoury Crate allows a local user to execute arbitrary code with elevated privileges via a crafted file replacement. Refer to the ' Security Update for ASUS Armoury Crate ' section on the ASUS Security Advisory for more information.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 30, 2026

Last Modified

July 31, 2026

Advisory Details (1)

Auto-updated Jul 30, 2026
No fix on record yet.
Web page

ASUS Security Advisory | Latest Vulnerability Update

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

Vendor Advisories for CVE-2026-16727(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 8× in last 7d / 54× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 216 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 116 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-18 04:00 UTCEG score recompute
  2. 2026-10-17 18:02 UTCEG score recompute
  3. 2026-10-17 18:02 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  4. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-12 16:30 UTCEG score recompute
  11. 2026-10-11 20:09 UTCEG score recompute
  12. 2026-10-11 17:21 UTCEG score recompute
  13. 2026-10-11 14:54 UTCEG score recompute
  14. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-10-06 23:55 UTCEG score recompute
  20. 2026-10-06 23:55 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  21. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-10-05 20:35 UTCEG score recompute
  23. 2026-10-05 20:35 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  24. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-10-04 23:59 UTCEG score recompute
Show 75 more
  1. 2026-10-04 23:59 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  2. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-04 06:45 UTCEG score recompute
  4. 2026-10-04 06:45 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  5. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-10-02 17:03 UTCEG score recompute
  7. 2026-10-02 17:03 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  8. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-01 14:44 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  10. 2026-10-01 03:19 UTCEG score recompute
  11. 2026-10-01 03:19 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  12. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-09-29 06:58 UTCEG score recompute
  15. 2026-09-29 06:58 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  16. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-09-28 06:31 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  18. 2026-09-27 19:06 UTCEG score recompute
  19. 2026-09-27 19:06 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  20. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-09-25 04:59 UTCEG score recompute
  23. 2026-09-25 04:59 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  24. 2026-09-24 08:58 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  25. 2026-09-23 21:34 UTCEG score recompute
  26. 2026-09-23 21:34 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  27. 2026-09-23 02:49 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  28. 2026-09-22 15:24 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  29. 2026-09-20 11:15 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  30. 2026-09-19 23:50 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  31. 2026-09-19 04:24 UTCEG score recompute
  32. 2026-09-19 04:24 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  33. 2026-09-18 19:27 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  34. 2026-09-18 14:55 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  35. 2026-09-18 01:25 UTCEG score recompute
  36. 2026-09-18 01:25 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  37. 2026-09-17 01:30 UTCEG score recompute
  38. 2026-09-17 01:30 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  39. 2026-09-16 14:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  40. 2026-09-16 05:40 UTCEG score recompute
  41. 2026-09-16 05:39 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  42. 2026-09-16 05:14 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  43. 2026-09-15 03:26 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  44. 2026-09-14 11:28 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  45. 2026-09-14 00:04 UTCEG score recompute
  46. 2026-09-14 00:04 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  47. 2026-09-13 16:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  48. 2026-09-13 12:39 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  49. 2026-09-13 01:13 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  50. 2026-09-12 13:49 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  51. 2026-09-12 02:25 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  52. 2026-09-11 15:00 UTCEG score recompute
  53. 2026-09-11 15:00 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  54. 2026-09-11 14:52 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  55. 2026-09-11 09:36 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  56. 2026-09-11 02:37 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  57. 2026-09-10 15:13 UTCEG score recompute
  58. 2026-09-10 15:13 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  59. 2026-09-10 09:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  60. 2026-09-10 03:49 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  61. 2026-09-09 07:24 UTCEG score recompute
  62. 2026-09-09 07:24 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  63. 2026-09-08 22:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  64. 2026-09-07 20:12 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  65. 2026-09-06 18:18 UTCEG score recompute
  66. 2026-09-06 18:18 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  67. 2026-09-06 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  68. 2026-09-06 06:40 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  69. 2026-09-05 18:53 UTCEG score recompute
  70. 2026-09-05 18:52 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  71. 2026-09-05 05:01 UTCEG score recompute
  72. 2026-09-05 05:01 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  73. 2026-09-04 11:37 UTCEG score recompute
  74. 2026-09-04 11:37 UTCGHSA enrichmentGHSA-479r-w7g7-fj9j · GitHub severity HIGH
  75. 2026-09-04 05:06 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile

Frequently asked(5)

What is CVE-2026-16727?
CVE-2026-16727 is a high-severity vulnerability; its CVE record was published on July 30, 2026. Concurrent Execution using Shared Resource with Improper Synchronization (“Race Condition”) in ASUS Armoury Crate allows a local user to execute arbitrary code with elevated privileges via a crafted file replacement. Refer to the ' Security Update for ASUS Armoury Crate ' section on the ASUS…
When was the CVE record for CVE-2026-16727 published?
The CVE record for CVE-2026-16727 was published on July 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 31, 2026; the record at its source may have been updated since.
Is CVE-2026-16727 actively exploited?
CVE-2026-16727 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16727?
CVE-2026-16727 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16727?
No fix for CVE-2026-16727 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (ASUSTeK Computer Incorporation) lists ASUS Armoury Crate versions V5.4.1 up to and including V6.4.12 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-16727 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-16727?

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