PatchSiren cyber security CVE debrief
CVE-2026-16489 jsforce CVE debrief
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, leading to OS command injection. The attack can only be performed from a local environment, and the exploit is publicly available. The project was informed of the problem early through an issue report but has not responded yet. Users should assess their exposure and consider updating to a patched version.
- Vendor
- jsforce
- Product
- jsforce
- CVSS
- LOW 1.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-22
- Original CVE updated
- 2026-07-22
- Advisory published
- 2026-07-22
- Advisory updated
- 2026-07-22
Who should care
Users of jsforce up to 3.10.16 should assess their exposure and consider updating to a patched version. Operators, platform administrators, vulnerability management teams, and security teams may be impacted by this vulnerability.
Technical summary
The vulnerability, CVE-2026-16489, is a low-severity issue with a CVSS score of 1.9. It allows for OS command injection through the _execCommand function in lib/registry/sfdx.js. Exploitation requires local access, and the attack can only be performed from a local environment. The vulnerability affects jsforce up to 3.10.16. Users should assess their exposure and consider updating to a patched version. The project was informed of the problem early through an issue report but has not responded yet. Evidence is limited, and defenders should verify the affected scope and vendor guidance.
Defensive priority
Low priority due to local attack vector and low CVSS score.
Recommended defensive actions
- Inventory and assess jsforce installations up to 3.10.16
- Consider updating to a patched version of jsforce
- Monitor for local exploitation attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record was published on 2026-07-22T00:17:30.887Z and was last modified on 2026-07-22T16:25:46.380Z. The NVD entry is currently Deferred. The vulnerability affects jsforce up to 3.10.16, and the attack can only be performed from a local environment. The project was informed of the problem early through an issue report but has not responded yet. Evidence is limited, and defenders should verify the affected scope and vendor guidance.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-16489 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-16489
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-16489 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-16489
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/jsforce/jsforce/
-
Source reference
Unverified legacy reference
URL: https://github.com/jsforce/jsforce/issues/1805
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/cve/CVE-2026-16489
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/submit/860031
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/380946
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/380946/cti
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.