First published: Mon May 12 2025(Updated: )
ToolHive is a utility designed to simplify the deployment and management of Model Context Protocol (MCP) servers. Due to the ordering of code used to start an MCP server container, versions of ToolHive prior to 0.0.33 inadvertently store secrets in the run config files which are used to restart stopped containers. This means that an attacker who has access to the home folder of the user who starts the MCP server can read secrets without needing access to the secrets store itself. This only applies to secrets which were used in containers whose run configs exist at a point in time - other secrets remaining inaccessible. ToolHive 0.0.33 fixes the issue. Some workarounds are available. Stop and delete any running MCP servers, or manually remove any runconfigs from `$HOME/Library/Application Support/toolhive/runconfigs/` (macOS) or `$HOME/.state/toolhive/runconfigs/` (Linux).
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
ToolHive | <0.0.33 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-47274 is considered a moderate severity vulnerability due to the potential exposure of secrets in configuration files.
To fix CVE-2025-47274, upgrade to ToolHive version 0.0.33 or later.
CVE-2025-47274 affects ToolHive versions prior to 0.0.33 that improperly store secrets in run config files.
The risks of CVE-2025-47274 include unauthorized access to sensitive secrets stored in the run config files.
Yes, CVE-2025-47274 specifically affects the ToolHive utility for managing Model Context Protocol servers.