The vulnerability allows an attacker to retrieve the full BIP‑39 seed phrase used to generate wallet key material because the seed is passed as a plain‐text parameter named 'mnemonic' in the JSON used by the MCP write tools. This data is included in the tool‑call payload and therefore may appear in any transport channel, logging system, or telemetry stream that backs the LLM provider and the MCP process, leading to disclosure of private keys and potential loss of funds. The flaw corresponds to information exposure weaknesses such as improper handling of sensitive data (CWE‑200), insecure transmission of credential material (CWE‑312), inadequate protection of secrets (CWE‑522), and log disclosure of secrets (CWE‑532).

The affected vendor is Dragonmonk111, product JunoClaw, an agentic AI platform built on Juno Network. All releases before 0.x.y-security-1 are vulnerable, as they accepted 'mnemonic' as an explicit parameter in every MCP write tool.

The CVSS score is 9.8, indicating a critical impact. While a definitive EPSS score is unavailable, the vulnerability is likely to be exploitable because the mnemonic travels in clear text and may be captured by any component that records or forwards the tool‑call JSON. The vulnerability is not listed in CISA KEV. It is presumed that an attacker with access to the LLM provider side or the MCP transport layer could read the seed. No additional requirement such as privileged access is stated, so the risk is high for users running unpatched versions.