CVE-2026-43992

JunoClaw: MCP write tools exposed raw BIP-39 mnemonic as a tool-call parameter

CVSS 9.8 CRITICALEPSS 0.2%CWE-200 CWE-312 CWE-522 CWE-532

Vexday Risk Score

28Low

SSVC decision (CISA)

Track

No exploitation signal → monitor

CVSS 9.8EPSS 0.2%KEV nãoPoC —Nuclei —Metasploit —Patch —

Lifecycle

12 May 2026Published on NVD

Recommendation: Monitor — no exploitation signal at the moment.

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.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Dragonmonk111 · junoclaw

Want to know if your infrastructure is exposed to this?

Talk to TrueHacking →

References

https://github.com/Dragonmonk111/junoclaw/commit/339701e https://github.com/Dragonmonk111/junoclaw/releases/tag/v0.x.y-security-1 https://github.com/Dragonmonk111/junoclaw/security/advisories/GHSA-j75q-8xvm-6c48