What is CVE-2026-110644?

CVE-2026-110644 is a critical-severity OS command injection vulnerability in nodejs-whisper (npm), affecting versions < 0.4.0. It is fixed in 0.4.0. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

How severe is CVE-2026-110644?

CVE-2026-110644 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of nodejs-whisper are affected by CVE-2026-110644?

nodejs-whisper (npm) versions < 0.4.0 is affected.

Is there a fix for CVE-2026-110644?

Yes. CVE-2026-110644 is fixed in 0.4.0. Upgrade to this version or later.

Is CVE-2026-110644 exploitable, and should I be worried?

Whether CVE-2026-110644 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-110644 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-110644 in nodejs-whisper

Q: How severe is CVE-2026-110644?

CVE-2026-110644 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of nodejs-whisper are affected by CVE-2026-110644?

nodejs-whisper (npm) versions < 0.4.0 is affected.

Q: Is there a fix for CVE-2026-110644?

Yes. CVE-2026-110644 is fixed in 0.4.0. Upgrade to this version or later.

Q: Is CVE-2026-110644 exploitable, and should I be worried?

Whether CVE-2026-110644 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-110644 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-110644?

Upgrade nodejs-whisper to 0.4.0 or later.

Summary

nodejs-whisper allows OS command injection through crafted audio file paths

nodejs-whisper through 0.3.1 contains an OS command injection vulnerability in convertToWavType() that allows attackers to execute commands by supplying crafted audio file paths. Attackers can provide file names containing $() command substitution or closing quotes, which are interpolated into an ffmpeg command run via shelljs exec(), executing OS commands with Node.js process privileges.

Impact

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2026-110644 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.4.0); upgrading removes the vulnerable code path.

Affected versions

nodejs-whisper (< 0.4.0)

Security releases

nodejs-whisper → 0.4.0 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade nodejs-whisper to 0.4.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-110644? CVE-2026-110644 is a critical-severity OS command injection vulnerability in nodejs-whisper (npm), affecting versions < 0.4.0. It is fixed in 0.4.0. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
How severe is CVE-2026-110644? CVE-2026-110644 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of nodejs-whisper are affected by CVE-2026-110644? nodejs-whisper (npm) versions < 0.4.0 is affected.
Is there a fix for CVE-2026-110644? Yes. CVE-2026-110644 is fixed in 0.4.0. Upgrade to this version or later.
Is CVE-2026-110644 exploitable, and should I be worried? Whether CVE-2026-110644 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-110644 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-110644? Upgrade nodejs-whisper to 0.4.0 or later.