# 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.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-j75q-8xvm-6c48

## 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-522 (Insufficiently Protected Credentials), CWE-312 (Cleartext Storage of Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43992 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-43992 in the wild and no public exploit code.

Affected product: Dragonmonk111 junoclaw. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43992/ (Markdown: https://insights.sbomify.com/CVE-2026-43992/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43992
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43992
- OSV: https://osv.dev/vulnerability/CVE-2026-43992

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43992/
Summaries are generated and may contain mistakes; the official description above is the record.