dbcve.org
CWE-942Weakness · CWE-942

CVE-2026-8919

HIGH · 7.2 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High
Remotely reachable No privileges 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

ASUS GameSDK contains a permissive cross-domain security policy that allows untrusted domains to make requests to the application's local service endpoint. A remote attacker can exploit this by tricking a user into visiting a crafted webpage that sends requests containing UNC paths to the local service, enabling theft of the user's NTLM hash for credential replay attacks.

MitigationRestrict the cross-domain policy to only allow trusted domains, or disable the permissive policy entirely. Additionally, consider implementing SMB signing or disabling NTLM authentication where possible to prevent NTLM hash theft.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if ASUS GameSDK is installed
    Look for ASUS GameSDK in the list of installed programs (Control Panel > Programs and Features) or check common installation directories such as C:\Program Files\ASUS\GameSDK or C:\Program Files (x86)\ASUS\GameSDK
    Affected if ASUS GameSDK is present on the system
  2. Identify the installed ASUS GameSDK version
    Check the version information of the GameSDK executable or DLL file by right-clicking the file in File Explorer and selecting Properties > Details, or use a tool like PowerShell to query installed software versions
    Affected if The installed version falls within any affected version range (compare against known vulnerable versions if available)
  3. Locate the cross-domain policy configuration file
    Search for XML policy files in the GameSDK installation directory, typically named crossdomain.xml or clientaccesspolicy.xml, or check the application configuration files for cross-domain settings
    Affected if A cross-domain policy file exists in the GameSDK directory
  4. Examine the cross-domain policy permissions
    Open the cross-domain policy XML file in a text editor and inspect the <allow-access-from> and <site-control> elements to determine if unrestricted or wildcard domains are permitted
    Affected if The policy contains domain='*' or domain attribute values allowing untrusted domains, or has no explicit restrictions on external domain access
  5. Verify the local service endpoint is exposed
    Check if the GameSDK local HTTP service is running and listening on a local port (commonly localhost or 127.0.0.1), using netstat or by reviewing the application documentation for default service ports
    Affected if The local GameSDK service is running and accessible via HTTP without authentication

The system is affected if ASUS GameSDK is installed with a permissive cross-domain policy that allows untrusted external domains to access the local service endpoint, enabling NTLM hash theft via crafted UNC path requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict the cross-domain policy to only allow trusted domains, or disable the permissive policy entirely. Additionally, consider implementing SMB signing or disabling NTLM authentication where possible to prevent NTLM hash theft.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8919 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8919 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data