CVE-2026-54051

CRITICALPre-NVD 9.99.9
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
Elevated
9.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 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.

CVSS v3
9.9
EG Score
9.9(low)
EG Risk
EPSS
29.6%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Jul 21, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Improper Neutralization of Special Elements used in an OS Command in network-ai · Advisory · Jovancoding/Network-AI · GitHub

https://github.com/Jovancoding/Network-AI/security/advisories/GHSA-qw6v-5fcf-5666
github_commit Patch Available

commit 379f77656b57 (Jovancoding/Network-AI)

Patch available: Jovancoding/Network-AI v5.9.1 (contains commit 379f77656b57)

https://github.com/Jovancoding/Network-AI/commit/379f77656b578144e03415c5b134d8309a4b5792

Vendor Advisories for CVE-2026-54051(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
network-ai5.9.1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 2× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-06-19 13:56 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54051?
CVE-2026-54051 is a critical vulnerability published on June 19, 2026. 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…
When was CVE-2026-54051 disclosed?
CVE-2026-54051 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54051 actively exploited?
CVE-2026-54051 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54051?
CVE-2026-54051 has a CVSS v3 base score of 9.9 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-54051?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54051, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54051

Explore →

Is Your Infrastructure Affected by CVE-2026-54051?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.