Code execution via session username buffer overflow
Published Jun 4, 2026 · Updated Jun 4, 2026
SEH-based buffer overflow in MobaXterm 12.1 allows context-dependent attackers to execute code through a crafted session file. The session parser copies an oversized username value without a sufficient bounds check, overwriting SEH control data used to redirect execution. The file must be imported and its malicious session opened, after which the payload runs with the MobaXterm user's privileges.
Summary
What happened
SEH-based buffer overflow in MobaXterm 12.1 allows context-dependent attackers to execute code through a crafted session file. The session parser copies an oversized username value without a sufficient bounds check, overwriting SEH control data used to redirect execution. The file must be imported and its malicious session opened, after which the payload runs with the MobaXterm user's privileges.
The record
- CVE
- CVE-2019-25741
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Mobatek
- Product
- MobaXterm
- Classifications
- CWE-120, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2026CVE publishedPublication date reported by the CVE source.
- Jun 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=12.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Mobatek MobaXterm 12.1 - Buffer Overflow (SEH)functional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo