{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-43992 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-43992 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-43992 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-43992 in the wild and no public exploit code.\n\nAffected product: Dragonmonk111 junoclaw. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-43992/ (Markdown: https://insights.sbomify.com/CVE-2026-43992/index.md)","id":"CVE-2026-43992","markdown":"https://insights.sbomify.com/CVE-2026-43992/index.md","name":"CVE-2026-43992","record":{"aliases":["GHSA-j75q-8xvm-6c48"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"AI agent platform","requires_auth":"none","summary":"Attackers can steal BIP-39 mnemonics exposed in LLM tool-call parameters, leading to full wallet compromise in JunoClaw AI agents.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"JunoClaw: MCP write tools exposed raw BIP-39 mnemonic as a tool-call parameter","id":"CVE-2026-43992","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"JunoClaw: SSRF in WAVS computeDataVerify allows cloud-metadata and internal-service access","id":"CVE-2026-43993"},"packages":[],"prev":{"headline":"JunoClaw: plugin-shell shell-injection bypass via substring blocklist","id":"CVE-2026-43991"},"products":["junoclaw"],"published":"2026-05-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-13","vendors":["Dragonmonk111"]},"summary":"Attackers can steal BIP-39 mnemonics exposed in LLM tool-call parameters, leading to full wallet compromise in JunoClaw AI agents.","url":"https://insights.sbomify.com/CVE-2026-43992/"}