CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-86540

CVE-2026-86540: Arbitrary Code Execution via LSP Binary Override in knowns

Amit Schendel
Amit Schendel
Senior Security Researcher

Oct 6, 2026·5 min read·13 visits

Executive Summary (TL;DR)

Unvalidated binary paths in workspace configuration files allow arbitrary command execution when opening a repository in knowns.

CVE-2026-86540 is a high-severity arbitrary code execution vulnerability in knowns, a repository management tool. The vulnerability occurs when the application parses and executes unvalidated language server binary overrides defined within a project's local configuration file.

Vulnerability Overview

The vulnerability CVE-2026-86540 describes an arbitrary code execution vulnerability in knowns, a developer tool and repository management application. The issue is located within the workspace configuration processing component, which handles project-level settings when a workspace directory is opened.\n\nIn vulnerable versions of the application, opening a directory containing a crafted .knowns/config.json configuration file allows the application to automatically parse and load settings without verification. The vulnerability is triggered during workspace startup, when the application attempts to initialize the Language Server Protocol (LSP) environment using paths specified in the configuration file.\n\nBecause the workspace initialization occurs automatically upon opening the directory, the application requires minimal user interaction to trigger the vulnerability beyond opening the workspace. This behavior exposes a significant attack surface to untrusted repositories, such as open-source projects or shared codebases.

Root Cause Analysis

The root cause of CVE-2026-86540 is a failure to sanitize and validate input in the settings.lsp.languages.<lang>.binary configuration property, which is mapped to the CWE-78 weakness class (Improper Neutralization of Special Elements used in an OS Command).\n\nWhen knowns initializes, the internal/lsp/detect.go component resolves the configured binary path via Detector.resolve. The resolution logic reads the user-supplied string from the local project configuration and instantiates a Binary object directly using this parameter without validation.\n\nBecause there is no verification that the user-supplied string matches a safe or pre-registered executable binary name, the application passes this unvalidated string to execution subshells. The execution is performed twice during the application workflow: first during workspace detection routines using functions like exec.LookPath, and second when starting the language server daemon via StartLanguage in internal/lsp/manager.go. Consequently, any system command or path to a local executable specified in the configuration file is executed with the privileges of the running application process.

Technical Diagram & Flow

The following diagram illustrates the technical execution flow from loading the malicious configuration to process execution under the user's privilege context.\n\nmermaid\ngraph LR\n A["Malicious Directory Opened"] --> B["Parse .knowns/config.json"]\n B --> C["Extract settings.lsp.languages.go.binary"]\n C --> D["Instantiate Binary with raw string"]\n D --> E["Detector.resolve checks binary"]\n E --> F["System executes payload via exec.LookPath / StartLanguage"]\n

Source Code Analysis

The vulnerability exists in the way internal/lsp/detect.go resolves overrides. In vulnerable versions, the application takes the raw string directly from the config file and creates a Binary structure.\n\nBelow is the vulnerable code block from version 0.29.1:\n\ngo\n// Vulnerable Code in internal/lsp/detect.go\nfunc (d *Detector) resolve(ctx context.Context, root string, lang Language, override string) (ServerCommand, bool) {\n\tbinaries := lang.Binaries\n\tif override != "" {\n\t\tbinary := Binary{Name: override} // Raw, unvalidated override string is accepted\n\t\tif len(binaries) > 0 {\n\t\t\tbinary.CheckArgs = append([]string(nil), binaries[0].CheckArgs...)\n\t\t}\n\t\tbinaries = []Binary{binary}\n\t}\n\t// ...\n}\n\n\nThe official patch in version 0.30.0 addresses this by introducing strict whitelist verification functions within internal/lsp/binary_override.go. The validation functions verify that the override string is an exact match for one of the pre-registered binaries associated with the corresponding language adapter.\n\nBelow is the patched implementation of the verification and resolution routines:\n\ngo\n// Patched Code in internal/lsp/binary_override.go\nfunc selectBinaryOverride(override string, candidates []Binary) (Binary, error) {\n\tif strings.TrimSpace(override) != override || override == "" {\n\t\treturn Binary{}, invalidBinaryOverride(override)\n\t}\n\tfor _, candidate := range candidates {\n\t\tif candidate.Name == override {\n\t\t return candidate, nil // Returns the binary only if it matches a registered candidate\n\t\t}\n\t}\n\treturn Binary{}, invalidBinaryOverride(override)\n}\n\n// Patched Code in internal/lsp/detect.go\nfunc (d *Detector) resolve(ctx context.Context, root string, lang Language, override string) (ServerCommand, bool) {\n\tbinaries := lang.Binaries\n\tif override != "" {\n\t\tbinary, err := selectBinaryOverride(override, binaries)\n\t\tif err != nil {\n\t\t return ServerCommand{}, false // Safe rejection on invalid binary name\n\t\t}\n\t\tbinaries = []Binary{binary}\n\t}\n\t// ...\n}\n

Exploitation Methodology

An attacker exploits this vulnerability by distributing a repository containing a malicious .knowns/config.json configuration file. The target workspace configuration is set to point the LSP binary to a command interpreter or local script.\n\nTo demonstrate this concept, a workspace is configured with the following content within .knowns/config.json:\n\njson\n{\n "settings": {\n "lsp": {\n "languages": {\n "go": {\n "binary": "/bin/sh"\n }\n }\n }\n }\n}\n\n\nWhen the victim opens the repository containing this file with knowns, the workspace manager reads the configuration. During the language server initialization phase, the workspace engine attempts to run the binary identified as /bin/sh to launch the language server, leading to execution of the shell instead of the language tool. If the attacker also bundles a target execution payload, they can force execution of specific scripts by specifying path parameters.

Impact Assessment

The vulnerability poses a high risk to environments running knowns on untrusted repositories. Successful exploitation results in arbitrary command execution under the context of the user running the application.\n\nAccording to CVSS v4.0 metrics, this vulnerability has a base score of 8.5. The attack vector is local because the user must interact with and open the directory containing the malicious configuration file. There are no special execution conditions, and no administrative privileges are required to exploit the flaw.\n\nBecause the code runs within the user's active session, the attacker gains full read, write, and execute permissions over all files accessible to that user account. This can lead to credential theft, compromise of sensitive source code, and subsequent privilege escalation on the host system.

Remediation & Mitigation Guidance

The primary remediation strategy is upgrading the application to version 0.30.0 or higher. Version 0.30.0 introduces structural input validation and prevents unauthorized binary overrides by rejecting non-registered executable names.\n\nIn environments where upgrading is not immediately possible, organizations must implement operational controls. Users must refrain from opening directories or repositories from untrusted sources, such as unverified public code repositories.\n\nAdditionally, system administrators should monitor process creation logs. Security tools should flag any instances where the application processes initiate system interpreters or command shells directly upon workspace loading.

Technical Appendix

CVSS Score
8.5/ 10
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
EPSS Probability
0.21%
Top 89% most exploited

Affected Systems

knowns

Affected Versions Detail

Product
Affected Versions
Fixed Version
knowns
knowns-dev
< 0.30.00.30.0
AttributeDetail
CWE IDCWE-78
Attack VectorLocal
CVSS v4.0 Base Score8.5
EPSS Score0.00212
Exploit Statusnone/low
ImpactArbitrary Code Execution (ACE)

MITRE ATT&CK Mapping

T1059Command and Scripting Interpreter
Execution
CWE-78
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

The application constructs an OS command using externally-influenced input without neutralizing or validating the input before passing it to execution subsystems.

Vulnerability Timeline

Security patch committed in d3989829fb5095666d23d005b2f78a082832a396
2026-08-13
GitHub Security Advisory GHSA-mc52-mwq4-vfx3 published
2026-09-07
Release of version 0.30.0 containing the fix
2026-09-07

References & Sources

  • [1]GitHub Security Advisory GHSA-mc52-mwq4-vfx3
  • [2]Fix Commit
  • [3]NVD Detail

More Reports

•11 minutes ago•CVE-2026-132277
5.3

CVE-2026-132277: Quadratic Memory Growth and Denial of Service in Inscriptis HTML-to-Text Library

CVE-2026-132277 (also tracked as GHSA-q87h-c5m7-659j) is an uncontrolled resource consumption and algorithmic complexity vulnerability in the Inscriptis Python library (versions 2.0.0 through 2.7.5). When rendering sibling HTML table elements inside a block-level parent container, the parser fails to pop the parent block's inline padding prefix from the internal canvas prefix stack upon closing the block. Consequently, each subsequent sibling table inherits and accumulates the indentation prefixes of all preceding tables. This causes the output string length and memory allocation of get_text() to grow quadratically with the number of sibling tables, allowing a compact untrusted HTML payload to trigger denial of service via memory exhaustion.

Amit Schendel
Amit Schendel
2 views•10 min read
•about 1 hour ago•CVE-2026-132276
5.9

CVE-2026-132276: Polynomial-Time Regular Expression Denial of Service (ReDoS) in wcmatch

CVE-2026-132276 (GHSA-53pm-wgxf-c6qf) is an algorithmic complexity and Regular Expression Denial of Service (ReDoS) vulnerability in the Python wcmatch wildcard and glob matching library prior to version 11.2. Under default flags, matching a non-matching attacker-controlled filename against a static developer-defined pattern containing multiple star (*) wildcards separated by literal delimiters causes polynomial-time backtracking O(n^k) in the compiled regular expression. A single 255-byte filename evaluated against a 5-star pattern consumes approximately 86 seconds of 100% CPU time, allowing unauthenticated attackers to induce severe availability degradation.

Alon Barad
Alon Barad
2 views•11 min read
•about 2 hours ago•CVE-2026-122244
7.7

CVE-2026-122244: Stored Cross-Site Scripting in Budibase Builder Formula Evaluation

CVE-2026-122244 (GHSA-r2q3-7m4h-63qg) is a high-severity cross-privilege Stored Cross-Site Scripting (XSS) vulnerability in Budibase prior to version 3.50.0. The flaw occurs due to defective character escaping in the JSON formatter utility combined with raw HTML rendering via Svelte's {@html} directive in the Budibase Builder interface. A low-privileged application user or an unauthenticated form visitor can store malicious HTML markup in a shared datasource, which subsequently executes arbitrary JavaScript in the browser session of an administrator or application builder inspecting Handlebars formula bindings.

Amit Schendel
Amit Schendel
4 views•9 min read
•about 3 hours ago•CVE-2026-122247
8.2

CVE-2026-122247: Unauthenticated Global-Admin and Database Creation via Tenant-Confusion Bypass in Budibase

A tenant-confusion vulnerability in the user initialization endpoint of the Budibase worker service (prior to version 3.50.0) allows unauthenticated remote attackers to bypass the one-time administrative setup guard. By supplying arbitrary tenant identifiers in POST requests to /api/global/users/init, an attacker can force the underlying CouchDB datastore to dynamically provision unlimited tenant databases and persist latent global administrator accounts. This results in datastore resource exhaustion, denial of service, and unauthorized administrative account creation inside non-default tenant contexts.

Amit Schendel
Amit Schendel
5 views•9 min read
•about 4 hours ago•CVE-2026-103026
8.1

CVE-2026-103026: Arbitrary Method Invocation and State Tampering in Paymenter via Livewire HasConfirmation Trait

Paymenter versions prior to 1.5.7 contain an arbitrary method invocation vulnerability within the base Livewire component architecture. The application includes a legacy trait, HasConfirmation, inside app/Livewire/Component.php, which is inherited across 36 client-facing Livewire components. This trait exposes a public remote procedure call (RPC) endpoint named executeConfirmedAction without access controls or method allowlisting. Remote attackers can invoke arbitrary methods on any inheriting component, including Livewire's internal fill() method, enabling them to bypass #[Locked] property protections and manipulate internal component state and hydrated Eloquent models.

Alon Barad
Alon Barad
5 views•9 min read
•about 5 hours ago•CVE-2026-104885
6.3

CVE-2026-104885: Cross-Realm MQTT Session Disconnect via Missing Authorization in OpenRemote

OpenRemote prior to version 1.31.0 contains a Missing Authorization vulnerability (CWE-862) in the user management REST API endpoint responsible for disconnecting active MQTT sessions. The disconnectUserSession method in UserResourceImpl fails to verify whether the requesting user owns the target MQTT session, holds administrative privileges, or belongs to the realm specified in the request path. As a result, any authenticated user who obtains a valid MQTT session identifier can forcefully terminate active MQTT connections belonging to other users or IoT devices across any tenant realm.

Amit Schendel
Amit Schendel
5 views•9 min read