IncidentMCP servers and tools
Corelight: a pinned MCP server can still pull fresh dependencies on every launch, so pinning the server does not pin what runs
James Lagermann of Corelight published on November 10, 2026 that an MCP server configured for one fixed release, with its configuration untouched, ran with 15 different dependency sets over five weeks; 23 of its 69 packages changed version, including the cryptography library, a JSON Web Token library and the MCP SDK. The assistants launched servers with uvx, which downloads and runs a Python package from one configuration line. For one community server pinned to a commit, the launcher installed from the declared dependencies and skipped the hash-pinned lock file, so about 60 packages were resolved fresh from PyPI at each rebuild; it was started 162 times in a week and the cache held 19 builds of the same release and commit. Of 35 MCP servers Corelight reviewed from two vendor catalogs and its lab, 23 had a recommended install that pulls dependencies from a public registry on every launch, install or image build. An npx-launched proxy for a hosted MCP service released six versions in one month, four within 14 hours, and one vendor's setup disabled TLS certificate checking for it. Five servers that Corelight froze (pinned to a commit, installed once from a hash-pinned lock file, launched directly, update checks off) kept the same package list over 457 starts in two weeks. Help Net Security reports that Lagermann notified the maintainers or the services sharing the servers; one company running an AI agent exchange changed its submission review and one vendor is repackaging its server.
Replay the attack step by step in the Learning Center
How it happened
- An MCP client config names a launcher such as uvx or npx, which fetches the server and its dependencies when it starts.
- Unless the lock file is used, every rebuild resolves new dependency versions from the public registry.
- So a server that looks pinned can run code that nobody reviewed, and a compromised package would arrive on its own.
Impact
No compromise is reported; 23 of 35 reviewed MCP servers install in a way that pulls fresh code from a public registry, leaving them open to a poisoned package.
The fix
Corelight advises pinning to a commit rather than a tag, installing from the hash-pinned lock file with hash checking, launching the installed server directly, turning off update checks at startup, scoping credentials to least access and naming an owner who re-locks on a schedule; maintainers should publish hash-pinned requirements, pin proxies and bound dependency ranges.
Lessons
- A pinned version in a config is not a pinned set of packages.
- Launchers that fetch at startup turn every agent start into a software install.
- Freezing has a cost too: frozen servers age, so re-lock and review them on a schedule.