# CVE-2026-105841: lrzsz before 0.13.0 OS Command Injection via lrz Pipe Mode

> Remote attackers can execute arbitrary commands on the receiving system by sending crafted filenames via the lrz pipe mode.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** AZL-106673, DEBIAN-CVE-2026-105841, GHSA-w9c3-4vq7-c452, UBUNTU-CVE-2026-105841

## What is CVE-2026-105841?

CVE-2026-105841 is a high-severity command injection vulnerability in Uwe Ohse lrzsz, published on 6 Oct 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

lrzsz before 0.13.0 contains an OS command injection vulnerability in the lrz receive utility's pipe mode that allows remote senders to execute commands by supplying crafted filenames. When lrz runs under a suffixed name such as lrztar, procheader() in src/lrz.c passes the unescaped ZMODEM/YMODEM filename to popen(), so shell metacharacters execute as the receiving user.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-105841 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105841 is a high-severity command injection vulnerability in Uwe Ohse lrzsz, published on 6 Oct 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-105841 in the wild and no public exploit code.

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

## Sources

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

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