Monday 16 November
Global

Your region, kept on this device.

Pinned MCP server picked up dependency changes over five weeks without config edits

Severity
Low
Sources
1

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

  1. No action needed.

Written by AI from the sources, checked against them

Full story timeline · 1 update

  1. Fri 13 NovemberYour pinned MCP server may not be as pinned as you thinkHelp Net Security

Who reported · 1 outlet

Help Net Security

Who and what is in it

Companies

Report a problem