OS Command Injection in JunoClaw (CVE-2026-43991)
Summary
OS command injection in JunoClaw (CVE-2026-43991). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.x.y-security-1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-43991 has been found in JunoClaw.
Successful exploitation can lead to full system takeover. CVSS score: 8.4/10.
What to do: upgrade JunoClaw to 0.x.y-security-1 or later.
If unsure, ask your IT team or search "JunoClaw CVE-2026-43991" on the vendor's site.
CVE-2026-43991 (JunoClaw) — CWE-78 / CVSS v3 8.4
Attack vector: local / unauthenticated / no user interaction
Patched: 0.x.y-security-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in JunoClaw.
Check the vendor advisory for the affected versions of JunoClaw.
Severity: High (CVSS 8.4/10). Successful exploitation can lead to full system takeover.
Update to 0.x.y-security-1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'JunoClaw' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'JunoClaw' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
JunoClawを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade JunoClaw to 0.x.y-security-1ステージング環境で 0.x.y-security-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com