vnotex VNote up to 4.11.x Tasks bufferName/selectedText os command injection

Summaryinfo

A vulnerability, which was classified as problematic, was found in vnotex VNote up to 4.11.x. The affected element is an unknown function of the component Tasks. The manipulation of the argument bufferName/selectedText results in os command injection. This vulnerability is known as CVE-2026-126042. Attacking locally is a requirement. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in vnotex VNote up to 4.11.x. Affected is some unknown functionality of the component Tasks. The manipulation of the argument bufferName/selectedText with an unknown input leads to a os command injection vulnerability. CWE is classifying the issue as CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command before it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-126042 since 11/10/2026. The exploitability is told to be easy. Local access is required to approach this attack. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1202 by the MITRE ATT&CK project.

Upgrading to version 4.12.0 eliminates this vulnerability. Applying the patch 0f5edd837d233a929d2a514a0e718d5d19c93918 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• vnotex

Name

• VNote

Version

• 4.0
• 4.1
• 4.2
• 4.3
• 4.4
• 4.5
• 4.6
• 4.7
• 4.8
• 4.9
• 4.10
• 4.11

Website

• Product: https://github.com/vnotex/vnote/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion