CVE-2026-43991: Dragonmonk111 junoclaw · OS Command Injection
Affects Dragonmonk111 junoclawSource CVE Database V5
Not known to be exploited · CVSS 8.4 High.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Dragonmonk111junoclaw | Affected
| Fixed in– |
AI-suggested
The vulnerability is fixed in junoclaw version 0.x.y-security-1. Users should upgrade to this version or later to remediate the issue. Patch status is not explicitly confirmed beyond the fix being included in this version, so users should verify with the vendor or official sources for the latest remediation guidance. Since this is not a cloud service, remediation depends on applying the fixed version. No vendor advisory content contradicts this recommendation.
Description
JunoClaw is an agentic AI platform built on Juno Network. Prior to 0.x.y-security-1, substring-based blocklist in plugin-shell's command-safety check could be bypassed by adversarial argument constructions, allowing unauthorized command execution on the host when combined with the companion advisory. Pre-patch, the check was applied to the raw command string rather than the parsed first token. This vulnerability is fixed in 0.x.y-security-1.