Vulnerability Database · npm · mcp-remote · Version
mcp-remote 0.0.13
0.0.13 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 31 Mar 2025
Licence MIT
Also known from other sources 0
Newer releases 124
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
mcp-remote 0.0.13 vulnerabilities
1 vulnerability cover mcp-remote 0.0.13. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2025-6514: mcp-remote OS Command Injection Vulnerability | 9.6 critical | 0.1.16 | 09 Jul 2025 |
Looking for another version, or everything Vulert holds for mcp-remote?
Questions
About mcp-remote 0.0.13
Is mcp-remote 0.0.13 vulnerable?
Yes. 1 vulnerability in the Vulert database cover mcp-remote 0.0.13: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.0.13 the latest release of mcp-remote?
No. 0.0.13 was published 31 Mar 2025, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor mcp-remote for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mcp-remote version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.