CVE-2026-11879
Description
MobaXterm Personal Edition 26.3 loads DLLs from a predictable temporary directory, enabling local attackers to execute arbitrary code via a malicious DLL.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
MobaXterm Personal Edition 26.3 loads DLLs from a predictable temporary directory, enabling local attackers to execute arbitrary code via a malicious DLL.
Vulnerability
MobaXterm Personal Edition (Portable) version 26.3 (Build 5154) contains a DLL search-order hijacking vulnerability (CWE-427). During startup, the application searches for specific DLLs in a predictable temporary directory before falling back to secure system paths. This allows an attacker with local access to place a specially crafted malicious DLL in that directory, which will be loaded automatically when the victim launches MobaXterm [1].
Exploitation
An attacker needs only local access to the system (low privileges) and the ability to write files to the predictable temporary directory. No user interaction beyond launching the application is required. The attacker places a malicious DLL in the temporary directory; upon the next launch of MobaXterm, the application loads the DLL, executing the attacker's code [1].
Impact
Successful exploitation results in arbitrary code execution in the context of the user running MobaXterm. This compromises the confidentiality, integrity, and availability of the affected system, as reflected by the CVSS v4.0 base score of 8.5 (AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) [1].
Mitigation
The vulnerability has been fixed by Mobatek in version 26.4. Users should upgrade to this version immediately. No workarounds are documented in the available references [1].
AI Insight generated on Jun 12, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
0No linked articles in our index yet.