EUVD-2026-47593
GHSA-qhc4-cxq6-mg2g
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Local-only attack vector with low-privilege requirement and no scope change; C/I/A set to Low consistent with CVSS 4.0 VC:L/VI:L/VA:L impact metrics.
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
Lifecycle Timeline
1DescriptionCVE.org
A vulnerability was identified in jsforce up to 3.10.16. This issue affects the function _execCommand in the library lib/registry/sfdx.js of the component SFDX Connection Registry. The manipulation leads to os command injection. The attack can only be performed from a local environment. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.
AnalysisAI
OS command injection in jsforce's SFDX Connection Registry component allows local low-privilege users to execute arbitrary shell commands by supplying unsanitized input to the _execCommand function in lib/registry/sfdx.js. All versions from 3.10.0 through 3.10.16 are affected. A public proof-of-concept exploit exists, and no patch has been released as the project maintainer has not responded to the responsible disclosure issue filed at GitHub issue #1805.
Technical ContextAI
jsforce is a widely-used JavaScript library providing a Salesforce API client for Node.js applications. The vulnerable code path resides in the SFDX Connection Registry (lib/registry/sfdx.js), which integrates with the Salesforce CLI (sfdx) to manage authenticated connections. The _execCommand function passes user-controllable input directly to OS-level command execution without adequate sanitization or escaping - a textbook CWE-77 (Improper Neutralization of Special Elements used in a Command) weakness. Attackers can inject shell metacharacters such as ;, &&, |, or backtick sequences to chain arbitrary commands alongside the intended SFDX invocation. Exploitation is constrained to the local environment because the SFDX integration is invoked from within the application runtime rather than exposed over a network interface.
RemediationAI
No vendor-released patch has been identified at time of analysis - the jsforce project was notified via GitHub issue #1805 but has not responded. The most effective compensating control is to disable or remove the SFDX Connection Registry integration (lib/registry/sfdx.js) from the jsforce deployment if SFDX CLI functionality is not operationally required; this eliminates the vulnerable code path entirely but removes SFDX-based authentication flows as a side effect. Where SFDX integration is needed, restrict local system access to trusted users only and enforce least-privilege process accounts for jsforce runtimes, so the jsforce process runs with minimal OS permissions and injected commands cannot escalate further. In CI/CD pipelines, sandbox jsforce execution within containers or isolated user accounts with no write access to sensitive paths. Monitor https://github.com/jsforce/jsforce/issues/1805 and the project release page at https://github.com/jsforce/jsforce/ for patch availability. Advisory reference: https://nvd.nist.gov/vuln/detail/CVE-2026-16489.
Same weakness CWE-77 – Command Injection
View allSame technique Command Injection
View allShare
External POC / Exploit Code
Leaving vuln.today