# CVE-2026-110641: @runnerty/executor-decompress through 3.1.1 OS Command Injection via Archive File Name

> Attackers can execute arbitrary OS commands via crafted archive filenames in the Runnerty decompress executor library.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-2v4p-6p6r-gr94

## What is CVE-2026-110641?

CVE-2026-110641 is a high-severity command injection vulnerability in @runnerty/executor-decompress, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

@runnerty/executor-decompress through 3.1.1 contains an OS command injection vulnerability that allows attackers to execute commands by supplying crafted archive file names to compress_file. Attackers who can name a file dropped into a watched directory can inject $() substitutions or unquoted shell metacharacters into shelljs exec() calls, running commands with Runnerty process privileges.

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

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


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

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

## Is CVE-2026-110641 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110641 is a high-severity command injection vulnerability in @runnerty/executor-decompress, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110641 in the wild and no public exploit code.

Affected product: @runnerty/executor-decompress. 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-110641/ (Markdown: https://insights.sbomify.com/CVE-2026-110641/index.md)
```

## Sources

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

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