{"answers":{"affected":"2 open source packages ship an affected version, including network-ai.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54051 exists.","fix":"Upgrade network-ai to 5.9.1 or later.","what":"CVE-2026-54051 is a critical command injection vulnerability in Jovancoding Network-AI, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54051 and fix it if it is affected.\n\nWhat it is: CVE-2026-54051 is a critical command injection vulnerability in Jovancoding Network-AI, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54051 exists.\n\nAffected packages and fixed versions:\n- network-ai (npm): affected all versions; fixed in 5.9.1\n- network-ai (npm): affected all versions; fixed in 5.9.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54051/ (Markdown: https://insights.sbomify.com/CVE-2026-54051/index.md)","id":"CVE-2026-54051","markdown":"https://insights.sbomify.com/CVE-2026-54051/index.md","name":"CVE-2026-54051","record":{"aliases":["GHSA-qw6v-5fcf-5666"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js agent orchestrator","requires_auth":"low_privilege","summary":"A compromised agent can execute arbitrary OS commands by bypassing the shell command allowlist via shell metacharacters in Network-AI.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"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; \u003canything\u003e`, 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 (`; \u0026 | $ ` ` ` ( ) \u003c \u003e { }` newline) or unterminated quote before the allowlist glob match; quoted metacharacters are preserved as literal argument data. Users should upgrade to `network-ai@5.9.1` or later. As defense in depth, avoid broad wildcard allowlist entries such as `node *` / `npm *` which are direct code execution by design.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Network-AI has an an OS Command Injection issue","id":"CVE-2026-54051","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"n8n-MCP: Cross-tenant access to workflow version backups in multi-tenant HTTP deployments","id":"CVE-2026-54052"},"packages":[{"ecosystem":"npm","fixed":["5.9.1"],"introduced":["0"],"last_affected":[],"package":"network-ai","purl":null,"source":"GHSA-qw6v-5fcf-5666"},{"ecosystem":"npm","fixed":["5.9.1"],"introduced":["0"],"last_affected":[],"package":"network-ai","purl":"pkg:npm/network-ai","source":"GHSA-qw6v-5fcf-5666"}],"prev":{"headline":"Sakai: IDOR in Profile Image Deletion Allows Any Authenticated User to Delete Any User's Profile Image","id":"CVE-2026-54050"},"products":["Network-AI"],"published":"2026-07-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-21","vendors":["Jovancoding"]},"summary":"A compromised agent can execute arbitrary OS commands by bypassing the shell command allowlist via shell metacharacters in Network-AI.","url":"https://insights.sbomify.com/CVE-2026-54051/"}