CVE-2026-126042: VNote command injection in tasks (high)

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.

Read the original 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.

cve.now Index

13Pcve.now Index 13 of 100 · methodology v3 · provisional

Exploitation0/40No signal
Exposure5/25Specific setups only
Reach?/20Unknown. No tracked technology or package matched
Severity8.3/10CVSS 7.3, total technical impact per CISA
No patch0/5No signal

What would change the score

Would score about 63 if added to CISA KEV
Would score about 58 if CISA's SSVC rates exploitation active
Would score about 23 if CISA's SSVC rates it automatable

How the score works · Rankings

What to do

Check whether your setup matches what the bug needs.
Affects VNote 3.11.0 up to but not including 4.12.0 A task references magic variables such as ${bufferName} or ${selectedText} A note filename or text containing shell metacharacters is present, such as in a shared notebook
Upgrade to a fixed version: 4.12.0.
Workaround: Do not run tasks on notebooks you did not create yourself

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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.

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.

Timeline

Nov 10, 2026, 4:37 PM UTCCVE published
Nov 10, 2026, 4:45 PM UTCFirst seen by cve.now
Nov 10, 2026, 9:04 PM UTCCISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
Nov 10, 2026, 9:04 PM UTCRecord last updated

Affected versions

vnotex VNote
From 3.11.0 · fixed in 4.12.0

Evidence 8

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-126042
Record
NVD · CVE-2026-126042

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126042

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: cve.now feed data

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: vulncheck.com

Which versions are affected by CVE-2026-126042?

VNote: from 3.11.0 before 4.12.0.Source: cve.now feed data

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: vulncheck.com

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: vulncheck.com

VNote 3.11.0 before 4.12.0 OS Command Injection via Tasks Magic Variables