Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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:XSummary
CVE-2025-12793 is a high-severity Untrusted Search Path (CWE-426) vulnerability in Asus Myasus. Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and CM-7 (Least Functionality) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-12793 is an uncontrolled DLL loading path vulnerability (CWE-426) in AsusSoftwareManagerAgent, a component associated with ASUS software such as MyASUS. Published on 2026-01-06, it has a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). The flaw allows the application to load a dynamic link library from an unintended, attacker-specified path.
A local attacker can exploit this vulnerability by influencing AsusSoftwareManagerAgent to load a malicious DLL from a location under their control, potentially resulting in arbitrary code execution with the privileges of the affected process. Exploitation requires local access to the system, low complexity, no special privileges, and user interaction, such as convincing a user to trigger the vulnerable functionality.
The ASUS Security Advisory, available at https://www.asus.com/security-advisory, addresses mitigation in the "Security Update for MyASUS" section, recommending users apply the provided updates to resolve the uncontrolled DLL loading issue.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-1095
Vulnerability Data
An uncontrolled DLL loading path vulnerability exists in AsusSoftwareManagerAgent. A local attacker may influence the application to load a DLL from an attacker-controlled location, potentially resulting in arbitrary code execution. Refer to the ' Security Update for MyASUS' section on…
more
the ASUS Security Advisory for more information.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Secure baseline settings can enforce absolute, organization-controlled paths for critical resources.
Least-functionality configuration can prohibit unapproved directories or executables from being reachable via search paths.
Engineering principles such as trusted paths, complete mediation, and least privilege directly require hard-coded or validated search paths instead of external ones.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Preventing execution of unauthorized code directly blocks the malicious binaries that an untrusted search path would load.
Secure development practices include avoiding or sanitizing externally influenced search paths in application code.
Hardened configuration baselines can enforce safe search paths and restrict environment variables that enable the weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can discover search-path issues but does not itself prevent them in production code.
Restricting software installation reduces the chance that untrusted binaries or libraries are placed in search paths.
Secure architecture principles include hard-coded or validated search paths and avoiding reliance on untrusted directories.
Secure coding standards require absolute paths or integrity-checked search paths, directly mitigating CWE-426.
Change-management processes can enforce review of path-handling changes, indirectly lowering risk.