# CVE-2019-25741: Mobatek MobaXterm 12.1 Buffer Overflow via Sessions File

> Remote attackers can execute arbitrary code by tricking users into importing a malicious session file in MobaXterm.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-288f-q89m-r9qr

## What is CVE-2019-25741?

CVE-2019-25741 is a critical memory corruption vulnerability in Mobatek MobaXterm, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2019-25741?


## How do I fix CVE-2019-25741?

No fix has been published for CVE-2019-25741 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-25741 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25741 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25741 and fix it if it is affected.

What it is: CVE-2019-25741 is a critical memory corruption vulnerability in Mobatek MobaXterm, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25741 exists.

Affected product: Mobatek MobaXterm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-25741/ (Markdown: https://insights.sbomify.com/CVE-2019-25741/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-25741
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-25741
- OSV: https://osv.dev/vulnerability/CVE-2019-25741

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-25741/
Summaries are generated and may contain mistakes; the official description above is the record.