CVE-2025-55294

Workarounds

If upgrading is not immediately possible, developers should:

• Strictly validate or whitelist acceptable format values (e.g., "jpeg", "png", "webp").
• Reject or sanitize any unexpected input before passing it to the library.
• Avoid allowing user-controlled data to reach the format option.

References

• CWE-78: OS Command Injection
• OWASP: Command Injection

This vulnerability is a command injection issue.
When user-controlled input is passed into the format option of the screenshot function, it is interpolated into a shell command without sanitization.
An attacker can craft malicious input such as:

{ format: "; echo vulnerable > /tmp/hello;" }

This results in arbitrary command execution with the privileges of the calling process.

Who is impacted:
Any application that accepts untrusted input and forwards it directly (or indirectly) into the format option is affected. If the library is used in a server-side context (e.g., API endpoints, web services), attackers may be able to exploit this remotely and without authentication, leading to full compromise of confidentiality, integrity, and availability.

CVSS v3.1 Base Score: 9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

CVE-2025-55294 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 (1.15.2); upgrading removes the vulnerable code path.

Kodem intelligence

The issue has been patched in version 1.15.2.
All users are strongly recommended to upgrade to 1.15.2 or later.
All earlier versions are vulnerable.

1. What is CVE-2025-55294? CVE-2025-55294 is a critical-severity command injection vulnerability in screenshot-desktop (npm), affecting versions < 1.15.2. It is fixed in 1.15.2. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
2. How severe is CVE-2025-55294? CVE-2025-55294 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.
3. Which versions of screenshot-desktop are affected by CVE-2025-55294? screenshot-desktop (npm) versions < 1.15.2 is affected.
4. Is there a fix for CVE-2025-55294? Yes. CVE-2025-55294 is fixed in 1.15.2. Upgrade to this version or later.
5. Is CVE-2025-55294 exploitable, and should I be worried? Whether CVE-2025-55294 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
6. What actually determines whether CVE-2025-55294 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.
7. How do I fix CVE-2025-55294? Upgrade screenshot-desktop to 1.15.2 or later.