# CVE-2026-73224: Electerm check folder size function may get attacked by unsafe folder name

> A malicious FTP or SFTP server can execute arbitrary commands on the user's machine via a crafted folder name during size calculation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-4wx8-4m69-8rw5

## What is CVE-2026-73224?

CVE-2026-73224 is a high-severity command injection vulnerability in electerm, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. Prior to 3.15.120, electerm allows a malicious FTP or SFTP server to execute arbitrary commands when a user downloads a crafted folder and invokes Properties and Calculate Size because calcLocal in src/client/components/sftp/file-info-modal.jsx inserts the server-controlled folder name into a du -sh shell command without safely escaping single quotes. This issue is fixed in version 3.15.120.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-73224?


## How do I fix CVE-2026-73224?

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

## Is CVE-2026-73224 being exploited?

There is no known exploitation of CVE-2026-73224 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73224 and fix it if it is affected.

What it is: CVE-2026-73224 is a high-severity command injection vulnerability in electerm, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-73224 in the wild and no public exploit code.

Affected product: electerm. 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-2026-73224/ (Markdown: https://insights.sbomify.com/CVE-2026-73224/index.md)
```

## Sources

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

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