{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-47274 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-47274 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-47274 is a low-severity vulnerability in stacklok toolhive, published on 12 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-47274 and fix it if it is affected.\n\nWhat it is: CVE-2025-47274 is a low-severity vulnerability in stacklok toolhive, published on 12 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-47274 in the wild and no public exploit code.\n\nAffected product: stacklok toolhive. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-47274/ (Markdown: https://insights.sbomify.com/CVE-2025-47274/index.md)","id":"CVE-2025-47274","markdown":"https://insights.sbomify.com/CVE-2025-47274/index.md","name":"CVE-2025-47274","record":{"aliases":["GHSA-xj5p-w2v5-fjm6"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MCP server manager","requires_auth":"low_privilege","summary":"An attacker with local access can read secrets from unencrypted run config files in ToolHive, exposing sensitive credentials.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.4,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"ToolHive stores secrets in the state store with no encryption","id":"CVE-2025-47274","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Brute Force Authentication Tags of CookieStore Sessions in Auth0-PHP SDK","id":"CVE-2025-47275"},"packages":[],"prev":{"headline":"setuptools has a path traversal vulnerability in PackageIndex.download that leads to Arbitrary File Write","id":"CVE-2025-47273"},"products":["toolhive"],"published":"2025-05-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-12","vendors":["stacklok"]},"summary":"An attacker with local access can read secrets from unencrypted run config files in ToolHive, exposing sensitive credentials.","url":"https://insights.sbomify.com/CVE-2025-47274/"}