# CVE-2026-68560: Wekan:hell Injection in External Antivirus Scanner Path via asyncExec

> Authenticated users can execute arbitrary commands on the server by injecting shell metacharacters into uploaded filenames when an external antivirus scanner is configured.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/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:** 19 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-x3xm-pxrv-jg7p

## What is CVE-2026-68560?

CVE-2026-68560 is a high-severity command injection vulnerability in wekan, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wekan is open source kanban built with Meteor. Prior to 9.75, models/fileValidation.js interpolated the uploaded fileObj.path into the administrator-configured externalCommandLine at its {file} placeholder and executed the result through asyncExec, which is promisify(exec) and invokes `/bin/sh -c`. On deployments with an external scanner configured, an authenticated user able to upload an attachment could place shell metacharacters such as command substitutions in the filename and execute commands as the Wekan server process. Version 9.75 adds shellQuote() and passes the file path as a POSIX single-quoted argument so shell metacharacters cannot escape the placeholder. This issue is fixed in version 9.75.

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

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


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

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

## Is CVE-2026-68560 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68560 is a high-severity command injection vulnerability in wekan, published on 19 Aug 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-68560 in the wild and no public exploit code.

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

## Sources

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

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