Pinned MCP server picked up dependency changes over five weeks without config edits
RESEARCHCorelightredteam/daily · 1 source
- Severity
- Low
- Sources
- 1
What happened
An MCP server configured for one fixed release on an administrator's workstation ran with 15 distinct dependency sets over five weeks, with configuration unchanged. 23 of its 69 packages changed version, including the cryptography library, the JSON Web Token library and the MCP SDK. The article identifies no CVEs or specific fixed versions. Defenders should not assume a pinned server release fixes its transitive dependencies, and should verify the resolved dependency tree on MCP hosts.
For security analysts · Written by AI from 1 source · Wrong?
What to do
- No action needed.
Written by AI from the sources, checked against them
Full story timeline · 1 update
Who reported · 1 outlet
Help Net Security
Who and what is in it
Companies