Wallet seed disclosure via MCP tool-call parameters
Published May 12, 2026 · Updated May 12, 2026
Sensitive information exposure in JunoClaw before 0.3.0 allows attackers to capture BIP-39 mnemonics from MCP tool-call data. Every MCP write-tool schema accepted a raw mnemonic parameter, placing the wallet seed in LLM request JSON, transport data, logs, and telemetry. Access to any such intermediate surface exposes full wallet signing credentials and permits control of the associated wallet.
Summary
What happened
Sensitive information exposure in JunoClaw before 0.3.0 allows attackers to capture BIP-39 mnemonics from MCP tool-call data. Every MCP write-tool schema accepted a raw mnemonic parameter, placing the wallet seed in LLM request JSON, transport data, logs, and telemetry. Access to any such intermediate surface exposes full wallet signing credentials and permits control of the associated wallet.
The record
- CVE
- CVE-2026-43992
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- Dragonmonk111
- Product
- JunoClaw
- Classifications
- CWE-200, CWE-522, CWE-532, CWE-312, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2026CVE publishedPublication date reported by the CVE source.
- May 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< v0.x.y-security-1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo