04
Corelight finds MCP server dependencies changing despite pinned configurations
Corelight reports that an MCP server configured for a fixed release used 15 different dependency sets over five weeks, with 23 of its 69 packages changing versions. The company says the launcher resolved dependencies afresh from a public package registry, bypassing the project’s hash-pinned lock file; MCP servers can hold users’ credentials and access management systems. In a review of 35 servers, Corelight found 23 with recommended installs that could pull public-registry dependencies on launches, installs or image builds.
What changed Following Corelight's notifications, one AI agent exchange expanded its submission security reviews to check for this dependency-resolution issue.
Why it matters Administrators using MCP servers to reach security-management systems may give newly resolved dependency code the same access. An unchanged server configuration therefore does not, by itself, establish that the code exercising those privileges is unchanged.
What to watch next One vendor is repackaging its MCP server. Whether that work removes the reported dependency exposure remains unresolved; the source gives no completion date.
HelpNet Security ↗