Key points
- CVE-2026-110644 affects nodejs-whisper versions up to 0.3.1 with a CVSS score of 9.3.
- The vulnerability stems from unsafe command interpolation in the convertToWavType function.
- Attackers can exploit crafted filenames containing shell substitution syntax to run OS commands.
The nodejs-whisper library contains a severe operating system command injection vulnerability that exposes applications to remote code execution. According to the National Vulnerability Database, versions up to 0.3.1 are affected by CVE-2026-110644. This flaw allows attackers to execute arbitrary commands on the host system by supplying maliciously crafted audio file paths to the library.
The vulnerability resides in the convertToWavType function, which processes audio files for conversion. The function interpolates user-supplied file names directly into an ffmpeg command executed via shelljs exec(). This design permits attackers to inject shell commands using techniques such as $() command substitution or closing quotes. The injected commands run with the same privileges as the Node.js process.
What we know
The National Vulnerability Database rates this issue as critical with a CVSS score of 9.3. The weakness is classified under CWE-78, which relates to improper neutralization of special elements used in an OS command. The affected software is maintained by ChetanXpro. The vulnerability specifically impacts how the library handles file path arguments during the audio conversion process. No patch has been confirmed in the source material for this specific version range.
Defender's checklist
- Audit your project dependencies for any version of nodejs-whisper equal to or lower than 0.3.1.
- Review code that accepts user-controlled file paths and passes them to shell execution functions.
- Implement strict input validation to reject filenames containing shell metacharacters like parentheses or quotes.
- Monitor system logs for unexpected ffmpeg processes or unusual command executions originating from your Node.js applications.
What analysts watch for
Teams usually examine how applications handle user-supplied filenames before passing them to system commands. Analysts check whether input validation occurs before shell execution to prevent injection. They look for patterns where user data is concatenated directly into command strings without sanitization. Persistence mechanisms often involve scripts that modify system configurations or create backdoors. Spread typically occurs through lateral movement using stolen credentials or exploiting other vulnerable services on the network.
What to do and how to stay safe: nodejs-whisper
- Identify all instances of nodejs-whisper in your dependency tree and verify their versions.
- Restrict file path inputs to alphanumeric characters and safe symbols to prevent shell injection.
- Use parameterized commands or libraries that avoid shell interpretation when executing external processes.
- Monitor for unauthorized command executions and isolate affected systems if suspicious activity is detected.
Step-by-step guide: Security Advisories: Small Business Patching Strategy
General security guidance from the Malware Chronicle newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the CVSS score for CVE-2026-110644?
The National Vulnerability Database assigns a CVSS score of 9.3, classifying it as critical.
Which versions of nodejs-whisper are affected?
All versions of nodejs-whisper up to and including 0.3.1 are vulnerable to this command injection flaw.
How do attackers exploit this vulnerability?
Attackers supply crafted audio file paths containing shell substitution syntax like $() or closing quotes to execute OS commands.
