CVE-2026-110640
9.8CriticalPublished 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-78
Impact
Remote attackers can execute arbitrary shell commands with the privileges of the Node.js process. They only need to submit untrusted input that reaches the filePath or whisperOptions.language parameters of the whisper() function.
Root cause
The createCppCommand() function concatenates unsanitized file paths and language parameters directly into a shell string executed by shelljs exec().
Affected systems
whisper-node through 1.1.1
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Fix & remediation
No fixed version is currently listed; check the repository pull request #64 for patches. As an immediate mitigation, sanitize or strictly validate filePath and language against an alphanumeric allowlist, or disallow untrusted inputs to whisper().
$ npm list whisper-nodeAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Whisper-node through 1.1.1 contains an OS command injection vulnerability that allows attackers to execute commands by supplying crafted filePath or whisperOptions.language values to whisper(). Attackers can inject shell metacharacters or $() substitution into the command string built by createCppCommand() and run via shelljs exec() to execute commands with Node.js process privileges.
References
- https://github.com/ariym/whisper-node/blob/c72944cfa48f5c74662ff17ee2dc1d5f7624393e/src/whisper.ts#L58
- https://github.com/ariym/whisper-node/blob/c72944cfa48f5c74662ff17ee2dc1d5f7624393e/src/whisper.ts#L8
- https://github.com/ariym/whisper-node/pull/64
- https://unpkg.com/whisper-node@1.1.1/dist/index.js
- https://www.vulncheck.com/advisories/whisper-node-through-1.1.1-os-command-injection-via-filepath-and-language