Unpinned MCP server dependencies let attackers steal API keys and admin credentials
- Severity
- High
- Sources
- 1
What happened
Corelight reports that MCP servers launched via uvx resolve transitive dependencies from PyPI at each environment rebuild, ignoring a hash-locked file. One server saw 23 of 69 packages change over five weeks, including cryptography and the MCP SDK. The article assigns no CVE, though it cites an mcp-remote flaw rated 9.6 on CVSS. Defenders should pin to commits, install from hash-pinned lock files, launch servers directly, disable start-up update checks and use least-privilege accounts. Hunt for DNS and TLS connections from AI assistant hosts to github.com, pypi.org, files.pythonhosted.org and registry.npmjs.org.
For security analysts · Written by AI from 1 source · Wrong?
What to do
- Pin MCP servers to a specific commit and install them from a hash-pinned lock file.
- Launch MCP servers directly and turn off start-up update checks.
- Give each MCP server its own least-privilege account and have a named owner review updates on a schedule.
- Check DNS and TLS logs for connections from AI assistant hosts to github.com, pypi.org and registry.npmjs.org.
Written by AI from the sources, checked against them
Full story timeline · 1 update
Who reported · 1 outlet
Who and what is in it
Companies
Products