CVE-2026-43992 JunoClaw: MCP write tools exposed raw BIP-39 mnemonic as a tool-call parameter
Attackers can steal BIP-39 mnemonics exposed in LLM tool-call parameters, leading to full wallet compromise in JunoClaw AI agents.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-43992?
CVE-2026-43992 is a critical vulnerability in Dragonmonk111 junoclaw, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
JunoClaw is an agentic AI platform built on Juno Network. Prior to 0.x.y-security-1, every MCP write tool (send_tokens, execute_contract, instantiate_contract, upload_wasm, ibc_transfer, etc.) accepted 'mnemonic: string' as an explicit tool-call parameter. The BIP-39 seed was consequently embedded in the LLM tool-call JSON, exposing it to any transport, log, or telemetry surface in the path between the LLM provider and the MCP process. This vulnerability is fixed in 0.x.y-security-1.
Which versions are affected by CVE-2026-43992?
How do I fix CVE-2026-43992?
No fix has been published for CVE-2026-43992 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-43992 being exploited?
There is no known exploitation of CVE-2026-43992 in the wild and no public exploit code.
Sources
Also known as GHSA-j75q-8xvm-6c48.