CVE-2026-8919

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (37th 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.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.2Exploit: None knownExposed services: Not assessed

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

Permissive Cross-domain Security Policy with Untrusted Domains in ASUS GameSDK allows a remote user to obtain a local user’s NTLM hash by convincing the user to visit a crafted web page that sends a request containing a UNC path to the application’s local service endpoint. This can result in information disclosure or data tampering, may cause GameSDK to become unavailable, and may also enable access to the victim’s information on other services. Refer to the ' Security Update for ASUS GameSDK  ' section on the ASUS Security Advisory for more information.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
48
EG Risk 48/100

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 (value × EchelonGraph’s weight)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend 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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 15, 2026

Last Modified

September 17, 2026

Advisory Details (1)

Auto-updated Jul 15, 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-8919(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 13× in last 7d / 45× 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 99 of 230 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 131 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-8919?
CVE-2026-8919 is a high-severity vulnerability; its CVE record was published on July 15, 2026. Permissive Cross-domain Security Policy with Untrusted Domains in ASUS GameSDK allows a remote user to obtain a local user’s NTLM hash by convincing the user to visit a crafted web page that sends a request containing a UNC path to the application’s local service endpoint. This can result in…
When was the CVE record for CVE-2026-8919 published?
The CVE record for CVE-2026-8919 was published on July 15, 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 September 17, 2026; the record at its source may have been updated since.
Is CVE-2026-8919 actively exploited?
CVE-2026-8919 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8919?
CVE-2026-8919 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-8919?
No fix for CVE-2026-8919 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 vendor advisories EchelonGraph has for CVE-2026-8919 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-8919?

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