Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 13 May 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 13 May 2026 11:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dragonmonk111
Dragonmonk111 junoclaw |
|
| Vendors & Products |
Dragonmonk111
Dragonmonk111 junoclaw |
Tue, 12 May 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | JunoClaw: MCP write tools exposed raw BIP-39 mnemonic as a tool-call parameter | |
| Weaknesses | CWE-200 CWE-312 CWE-522 CWE-532 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-13T14:38:16.906Z
Reserved: 2026-05-04T20:24:31.917Z
Link: CVE-2026-43992
Updated: 2026-05-13T14:34:08.439Z
Status : Deferred
Published: 2026-05-12T17:16:21.240
Modified: 2026-05-13T17:00:37.097
Link: CVE-2026-43992
No data.
OpenCVE Enrichment
Updated: 2026-05-13T10:38:38Z