CRITICAL 9.8

CVE-2019-25741: MobaXterm 12.1 SEH Buffer Overflow – Critical RCE Vulnerability

MobaXterm 12.1 has a critical vulnerability in how it handles session files. When a user imports a specially crafted session file—a common workflow for administrators managing multiple remote connections—an attacker can overflow the username field to inject malicious code. If the session file is opened and executed, the attacker gains immediate code execution with the privileges of the user running MobaXterm, potentially enabling remote shell access and full system compromise.

Source data · NVD / CISA · public domain

CVSS
3.1 · 9.8 CRITICAL · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weaknesses (CWE)
CWE-120
Affected products
0 configuration(s)
Published / Modified
2026-06-04 / 2026-06-17

NVD description (verbatim)

Mobatek MobaXterm 12.1 contains a structured exception handling (SEH) based buffer overflow vulnerability in the username field of session files that allows remote attackers to execute arbitrary code. Attackers can craft a malicious MobaXterm sessions file with overflow data that triggers the vulnerability when imported and executed, enabling reverse shell execution with user privileges.

3 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2019-25741 is a structured exception handling (SEH) based buffer overflow affecting MobaXterm 12.1's session file parser. The vulnerability exists in the username field processing when a .mxtsessions file (or similar session configuration) is imported. The lack of bounds checking allows an attacker to craft a malicious session file with oversized username data that overwrites the SEH chain on the stack. By controlling the SEH handler pointer, the attacker can redirect execution to shellcode embedded in the overflow payload, achieving arbitrary code execution. The attack requires user interaction (session import and execution) but no authentication or elevated privileges on the target system.

Business impact

MobaXterm is widely used by system administrators, DevOps engineers, and IT support staff for remote connection management across Windows networks. A successful exploit could allow an attacker to establish a foothold in an organization's administrative tier, potentially leading to lateral movement, credential theft, and persistent access to critical infrastructure. The attack surface is particularly dangerous because session files are often shared or downloaded from untrusted sources (e.g., vendor documentation, shared repositories, email), making social engineering a viable attack vector. Organizations relying on MobaXterm for secure access management face significant exposure if version 12.1 is deployed.

Affected systems

MobaXterm version 12.1 is affected. The vulnerability is triggered during session file import and execution, meaning any system running this version and opening a crafted session file is at risk. Windows systems are the primary target, as MobaXterm is a Windows-native SSH and terminal client, though versions for macOS and Linux may also be affected depending on the codebase structure. No vendor product vulnerability confirmation data was available at the time of this intelligence; verify the exact scope via Mobatek's official security advisory.

Exploitability

Exploitability is high. The attack requires crafting a malicious session file and socially engineering a user into opening it—both achievable tasks. No authentication, no special permissions, and no user system interaction beyond opening a file is needed once the payload is delivered. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U) reflects network-accessible attack surface with low attack complexity. However, the requirement for file import introduces a small friction point; this is not a network-facing remote code execution without user action. Proof-of-concept development would be straightforward for skilled attackers, though public exploit code availability should be monitored.

Remediation

Immediately upgrade MobaXterm to a patched version released by Mobatek after version 12.1. Check Mobatek's official security advisory for the specific version number and availability. Until patching is possible, implement defense-in-depth controls: disable automatic session file imports, restrict user ability to open untrusted session files via group policy or AppLocker, use application whitelisting to prevent unsigned binary execution, and conduct user awareness training on the risks of opening session files from unknown sources. For high-risk environments, consider retiring MobaXterm 12.1 in favor of an alternative SSH client pending patch availability.

Patch guidance

Contact Mobatek directly or visit their official support portal for the patched version number and distribution method. Given the critical severity (CVSS 9.8), treat patching as a priority and verify via official channels rather than third-party repositories. Document the patch version in your change management system and test in a non-production environment before enterprise rollout. Session files from pre-patch systems should be treated as untrusted; do not import them into patched versions without manual review or re-creation in a secure manner.

Detection guidance

Monitor for .mxtsessions file activity, particularly unusual import or execution events. Endpoint detection and response (EDR) tools should flag SEH exploitation attempts, stack pivots, or unexpected shellcode patterns in MobaXterm memory. Log process execution and child processes spawned by MobaXterm—reverse shell activity would manifest as unexpected outbound connections or spawned cmd.exe/PowerShell instances. Network intrusion detection systems should monitor for outbound shell traffic that could indicate successful exploitation. Additionally, audit session file creation and modification on shared drives or email systems where attackers might drop payloads.

Why prioritize this

CRITICAL severity warrants immediate prioritization due to (1) CVSS 9.8 reflecting complete system compromise potential, (2) high prevalence of MobaXterm among administrative users, (3) low attack complexity and social engineering feasibility, (4) potential for supply chain attacks via shared session files, and (5) the direct path to reverse shell execution. Organizations should treat this as a tier-1 security incident risk requiring executive awareness and rapid remediation planning.

Risk score, explained

The CVSS 3.1 score of 9.8 (CRITICAL) reflects a network-accessible buffer overflow with no authentication required and complete impact across confidentiality, integrity, and availability. The SEH exploitation mechanism is reliable and does not depend on system mitigations like ASLR in earlier Windows versions. Attack complexity is low—the malicious file simply needs to be opened—and the attack applies to all instances of the software. The only limiting factor is the requirement for user interaction (file import), which prevents a pure 10.0 score but does not materially reduce real-world risk given the commonality of session file sharing in IT environments.

Frequently asked questions

Can this vulnerability be exploited without user interaction?

No. An attacker must trick or socially engineer a user into importing and executing a crafted session file. This is not a worm-like vulnerability that propagates automatically. However, session files are frequently shared in administrative contexts (documentation, team repositories, configuration backups), making the user interaction barrier relatively low in practice.

Does patching require system restart or MobaXterm reinstallation?

Verify with Mobatek's advisory, but typical application patches do not require a system restart. You may need to close all MobaXterm instances before upgrading. Session files and settings are usually preserved during upgrades; however, test this assumption in your environment before enterprise deployment.

Are older versions of MobaXterm also vulnerable?

The advisory specifically identifies version 12.1. Earlier and later versions may have different vulnerability profiles. Check Mobatek's advisory to confirm which versions are affected. Do not assume that upgrading beyond 12.1 automatically resolves this; confirm the patch version number with the vendor.

Can we detect whether this vulnerability has been exploited in our environment?

Look for suspicious MobaXterm process behavior (child processes, unexpected network connections), SEH exploitation artifacts in event logs or EDR telemetry, and reverse shell indicators (outbound shell connections, unexpected PowerShell/cmd.exe spawning). However, if the attack was successful and a reverse shell was established, it may have covered its tracks; forensic analysis of MobaXterm crash dumps or memory would be needed for full confirmation.

This intelligence is provided for informational purposes to assist security professionals in risk assessment and mitigation planning. The vulnerability details, CVSS score, and affected versions are based on official CVE data. Organizations should verify all patch version numbers, availability dates, and affected product scope directly with Mobatek's official security advisory before implementing remediation. No exploit code or weaponized proof-of-concept is provided herein. SEC.co does not warrant the completeness or accuracy of derivative analyses; conduct your own testing in controlled environments. Always follow your organization's change management and testing procedures before deploying patches to production systems. Source: NVD (public-domain), retrieved 2026-07-14. Analysis generated by SEC.co (claude-haiku-4-5).

Preview — this page is review (quality 0.935). high-value: hold for review.