OS Command Injection in network-ai (CVE-2026-54051)
Summary
OS command injection in network-ai (CVE-2026-54051). Successful exploitation can lead to full system takeover. Exploitable via SandboxPolicy.isCommandAllowed. Mitigation: upgrade to 5.9.1 or later.
Original description
The description as published by the source.
Network-AI is a TypeScript/Node.js multi-agent orchestrator. Prior to version 5.9.1, the agent sandbox gates shell commands behind an allowlist (SandboxPolicy.isCommandAllowed), which THREAT_MODEL.md calls the main control against a compromised agent (Adversary 3.2). The allowlist glob-matches the whole command string, but ShellExecutor runs that string through /bin/sh -c. So any wildcard allow such as git *, npm * or node * also matches git status; , and a scoped command becomes arbitrary execution. The issue is fixed in v5.9.1. ShellExecutor now executes via spawn(file, args, { shell: false }) using a quote-aware parsed argv, so no shell is invoked. SandboxPolicy.isCommandAllowed and the new SandboxPolicy.tokenizeCommand reject any unquoted shell metacharacter (; & | $ ( ) < > { }newline) or unterminated quote before the allowlist glob match; quoted metacharacters are preserved as literal argument data. Users should upgrade tonetwork-ai@5.9.1or later. As defense in depth, avoid broad wildcard allowlist entries such asnode */npm *` which are direct code execution by design.
Source: GitHub Security Advisories (Global) 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-54051 has been found in network-ai.
Attackers can target a specific entry point like SandboxPolicy.isCommandAllowed over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade network-ai to 5.9.1 or later.
If unsure, ask your IT team or search "network-ai CVE-2026-54051" on the vendor's site.
CVE-2026-54051 (network-ai) — CWE-78 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: SandboxPolicy.isCommandAllowed / ShellExecutor / isCommandAllowed / globMatch
Patched: 5.9.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 network-ai. Attackers reach the vulnerable code path via SandboxPolicy.isCommandAllowed.
Check the vendor advisory for the affected versions of network-ai. Attack surface: SandboxPolicy.isCommandAllowed / ShellExecutor / isCommandAllowed / globMatch.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to 5.9.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 'network-ai' . 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 'network-ai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
network-aiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade network-ai to 5.9.1ステージング環境で 5.9.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com