A Guth Labs publication ↗
Back to News

Corelight finds hidden dependency changes beneath pinned MCP servers

Corelight has documented a deployment risk in AI assistants connected to administrative tools: a server can keep the same release identifier while its supporting code changes. The company’s November 10, 2026 study concerns installation choices, not a newly disclosed flaw in the Model Context Protocol itself. Research

In one examined setup, a pinned server produced 15 dependency combinations across 19 environment builds over five weeks. Corelight says 23 of 69 packages changed. The host was not compromised. Its wider review found registry-dependent installation instructions for 23 of 35 servers, a selected sample rather than a measurement of the entire ecosystem.

The distinction is especially relevant when an assistant’s connectors carry powerful credentials. Reviewing only the top-level release can miss changes below it. Corelight reports that freezing complete environments stopped the observed drift, but warns that deliberate vulnerability review and updates must continue.

Caching and locking answer different questions

Astral’s own documentation explains that uvx runs tools in temporary, isolated environments stored in its cache. Later invocations normally reuse the cached tool unless a different version is requested or the cache is pruned or refreshed. That is more specific than saying every launch downloads a fresh copy. A cached environment can disappear and be recreated. uv tool behavior

Astral also documents separate commands for compiling requirements into a lockfile and synchronizing an environment with that lockfile. Those mechanisms address dependency reproducibility, while caching primarily avoids repeated setup work. Locking tools

For operators, the useful question is what exact dependency set a connector runs today, who approves changes to it, and what that process can access. An unchanged release label alone cannot answer those questions. Treating a frozen environment as maintenance-free would create a different problem: predictable code can still become outdated code.

Sources and citations

Revision history

Published .