Vulnerability · Published May 12, 2026 · Assigned by GitHub_M

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

Critical 9.8

In plain English

A critical-severity information exposure in junoclaw from Dragonmonk111. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 13% of all known vulnerabilities).

Severity (CVSS 3.1)9.8Critical

Exploit odds (30 days)0.2%top 86.7% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

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.

Affected products (as reported)

Vendor	Product	Versions
Dragonmonk111	junoclaw	< v0.x.y-security-1

Weakness: CWE-200, CWE-312, CWE-522, CWE-532 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

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