CVE-2025-58358

mcp-markdownify-server vulnerable to command injection in pptx-to-markdown tool

Command Injection / Remote Code Execution (RCE)

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-58358 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and user interaction required. 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.0.2); upgrading removes the vulnerable code path.

Kodem intelligence

To mitigate this vulnerability, I suggest to avoid using child_process.exec with untrusted input. Instead, use a safer API such as child_process.execFile, which allows you to pass arguments as a separate array - avoiding shell interpretation entirely.
Note: given that the uvPath can be relative (i.e. "~/.local/bin/uv"), I suggest to consider untildify (https://www.npmjs.com/package/untildify) package to convert a tilde path to an absolute path before passing to child_process.execFile. Something like the following (not tested):

import { execFile } from "child_process";
import untildify from 'untildify';
const execAsync = promisify(execFile);
const { stdout, stderr } = await execAsync(untildify(uvPath),["run", markitdownPath, filePath]);

1. What is CVE-2025-58358? CVE-2025-58358 is a high-severity command injection vulnerability in mcp-markdownify-server (npm), affecting versions <= 0.0.1. It is fixed in 0.0.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-58358? CVE-2025-58358 has a CVSS score of 7.5 (High). 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 mcp-markdownify-server are affected by CVE-2025-58358? mcp-markdownify-server (npm) versions <= 0.0.1 is affected.
4. Is there a fix for CVE-2025-58358? Yes. CVE-2025-58358 is fixed in 0.0.2. Upgrade to this version or later.
5. Is CVE-2025-58358 exploitable, and should I be worried? Whether CVE-2025-58358 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-58358 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-58358? Upgrade mcp-markdownify-server to 0.0.2 or later.