JunoClaw: upload_wasm accepted arbitrary filesystem paths without validation

published 2026-05-12 5 mo ago modified 2026-10-26 13 d ago also EUVD-2026-29538

cvss: 8.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 3%
public exploits: 0; none known

JunoClaw is an agentic AI platform built on Juno Network. Prior to 0.x.y-security-1, the upload_wasm MCP tool accepted a filesystem path from the agent and uploaded whatever bytes the path resolved to, with no validation of location, symlink target, file size, or file format. This vulnerability is fixed in 0.x.y-security-1.

Patch / fix

links 2

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 5 mo ago (2026-05-14)

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.5	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L

Affected products

Dragonmonk111 junoclaw

Classification

Weakness

CWE-20 Improper Input Validation
CWE-22 Improper Limitation of a Pathname to a Restricted Directory
CWE-59 Improper Link Resolution Before File Access
CWE-73 External Control of File Name or Path

References

Sources

CVE List CVE-2026-43989
NVD CVE-2026-43989

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary