# CVE-2026-86022: VNote: Argument injection to arbitrary command execution via crafted note filename in external-program handling

> Attackers can execute arbitrary commands by crafting note filenames with quotes, exploiting external program handling in VNote.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-6m2r-wm6v-c8qp

## What is CVE-2026-86022?

CVE-2026-86022 is a high-severity command injection vulnerability in vnotex vnote, published on 13 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

VNote is a note-taking platform. Prior to 4.3.0, SessionConfig::ExternalProgram::fetchCommand wraps a note path in double quotes and substitutes it into a command string that QProcess::start(const QString&) reparses into arguments through ProcessUtils::startDetached. The automatic path in src/controllers/viewareacontroller.cpp and the Open With path in src/controllers/notebooknodecontroller.cpp both reach this sink. On Linux and macOS, an attacker-controlled double quote in a POSIX note filename can terminate the quoted path and add arguments to the victim's configured external program. If the configured program supports an argument that executes commands, such as the vim or gvim -c option, the injected arguments can execute arbitrary commands as the user. This issue is fixed in version 4.3.0.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-86022 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86022 is a high-severity command injection vulnerability in vnotex vnote, published on 13 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86022 exists.

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

## Sources

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

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