# CVE-2026-43990: JunoClaw: plugin-shell shell-metacharacter injection via shell wrapper

> Attackers can execute arbitrary commands by injecting shell metacharacters into agent-supplied arguments in the JunoClaw plugin-shell component.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-gpvm-3chf-2649

## What is CVE-2026-43990?

CVE-2026-43990 is a high-severity command injection vulnerability in Dragonmonk111 junoclaw, published on 12 May 2026. It can only be exploited from the same machine or local network, 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, plugin-shell's run_command wrapped every agent-supplied command in 'sh -c' / 'cmd /C' and passed the full argument string to the shell's parser, allowing shell metacharacters in agent-supplied arguments to be interpreted as command syntax. This vulnerability is fixed in 0.x.y-security-1.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-43990?


## How do I fix CVE-2026-43990?

No fix has been published for CVE-2026-43990 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-43990 being exploited?

There is no known exploitation of CVE-2026-43990 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-43990 is a high-severity command injection vulnerability in Dragonmonk111 junoclaw, published on 12 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-43990 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-43990/ (Markdown: https://insights.sbomify.com/CVE-2026-43990/index.md)
```

## Sources

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

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