CVE-2026-54051

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-19. A secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-46003 (ENISA EUVD) · GHSA-qw6v-5fcf-5666 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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 [email protected] 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.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 19, 2026

Last Modified

October 24, 2026

Advisory Details (2)

Auto-updated Nov 9, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)🟡 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.10.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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmnetwork-ai @ 5.9.1 (fixes < 5.9.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
network-ai—
  • every version up to 5.9.1: fixed in 5.9.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 188 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 88 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-13 07:26 UTCEchelonGraph re-scored
  3. 2026-11-13 07:26 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-11-12 07:00 UTCEchelonGraph re-scored
  6. 2026-11-12 07:00 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
  7. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-11-11 06:37 UTCEchelonGraph re-scored
  9. 2026-11-11 06:37 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
  10. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-11-10 06:15 UTCEchelonGraph re-scored
  12. 2026-11-10 06:15 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-11-09 05:53 UTCEchelonGraph re-scored
  15. 2026-11-09 05:53 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
  16. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-11-08 05:31 UTCEchelonGraph re-scored
  18. 2026-11-08 05:31 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
  19. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-11-07 05:08 UTCEchelonGraph re-scored
  21. 2026-11-07 05:08 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
  22. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-11-06 11:55 UTCOSV refresh
  24. 2026-11-06 04:46 UTCEchelonGraph re-scored
  25. 2026-11-06 04:46 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
Show 75 more
  1. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-11-05 04:24 UTCEchelonGraph re-scored
  3. 2026-11-05 04:24 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-11-04 04:01 UTCEchelonGraph re-scored
  6. 2026-11-04 04:01 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
  7. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-11-03 03:38 UTCEchelonGraph re-scored
  9. 2026-11-03 03:38 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
  10. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-11-02 03:15 UTCEchelonGraph re-scored
  12. 2026-11-02 03:15 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-11-01 07:45 UTCGHSA enrichmentGHSA-qw6v-5fcf-5666 · GitHub severity CRITICAL · GitHub CVSS 9.9
  15. 2026-11-01 07:45 UTCEchelonGraph re-scored
  16. 2026-11-01 02:53 UTCEchelonGraph re-scored
  17. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-31 02:31 UTCEchelonGraph re-scored
  19. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-30 02:08 UTCEchelonGraph re-scored
  21. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-29 01:46 UTCEchelonGraph re-scored
  23. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-28 01:23 UTCEchelonGraph re-scored
  25. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  26. 2026-10-27 00:55 UTCEchelonGraph re-scored
  27. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  28. 2026-10-25 20:48 UTCEchelonGraph re-scored
  29. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-10-25 14:20 UTCEchelonGraph re-scored
  31. 2026-10-24 20:26 UTCEchelonGraph re-scored
  32. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  33. 2026-10-23 22:36 UTCEchelonGraph re-scored
  34. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  35. 2026-10-22 22:13 UTCEchelonGraph re-scored
  36. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  37. 2026-10-21 21:50 UTCEchelonGraph re-scored
  38. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  39. 2026-10-20 21:22 UTCEchelonGraph re-scored
  40. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  41. 2026-10-19 20:59 UTCEchelonGraph re-scored
  42. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  43. 2026-10-18 19:27 UTCEchelonGraph re-scored
  44. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  45. 2026-10-18 03:31 UTCEchelonGraph re-scored
  46. 2026-10-17 19:02 UTCEchelonGraph re-scored
  47. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  48. 2026-10-16 18:38 UTCEchelonGraph re-scored
  49. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  50. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  51. 2026-10-15 15:15 UTCEchelonGraph re-scored
  52. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  53. 2026-10-14 09:39 UTCEchelonGraph re-scored
  54. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  55. 2026-10-13 07:23 UTCEchelonGraph re-scored
  56. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  57. 2026-10-12 15:57 UTCEchelonGraph re-scored
  58. 2026-10-11 19:40 UTCEchelonGraph re-scored
  59. 2026-10-11 16:55 UTCEchelonGraph re-scored
  60. 2026-10-11 14:18 UTCEchelonGraph re-scored
  61. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  62. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  63. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  64. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  65. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  66. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  67. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  68. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  69. 2026-10-03 14:49 UTCOSV refresh
  70. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  71. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  72. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  73. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  74. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  75. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 49th percentile

Frequently asked(5)

What is CVE-2026-54051?
CVE-2026-54051 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-54051 published?
The CVE record for CVE-2026-54051 was published on June 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-54051 actively exploited?
CVE-2026-54051 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54051?
CVE-2026-54051 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54051?
A fix for CVE-2026-54051 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54051 are linked in the Vendor Advisories panel on this page.

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.