Vulnerability in network-ai (CVE-2026-42856)
Summary
Vulnerability in network-ai (CVE-2026-42856). Risk of unauthorized operations or information disclosure. Exploitable via GET /tools. Mitigation: upgrade to 5.1.3 or later.
Original description
The description as published by the source.
Network-AI is a TypeScript/Node.js multi-agent orchestrator. Prior to 5.1.3, the MCP HTTP transport accepts JSON-RPC tools/call requests with no authentication, session, origin, or token check, and dispatches them directly to the orchestrator's tool registry. The default bind address is 0.0.0.0. As a result, any party with network reachability to the service can enumerate and invoke privileged management tools. This vulnerability is fixed in 5.1.3.
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-42856 has been found in network-ai.
Attackers can target a specific entry point like GET /tools over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade network-ai to 5.1.3 or later.
If unsure, ask your IT team or search "network-ai CVE-2026-42856" on the vendor's site.
CVE-2026-42856 (network-ai) — CWE-306
Attack surface: GET /tools / c344f2053eb0d49395988f803bf92f2a86b2a0d0 / config_get / agent_list
Patched: 5.1.3 — 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.
A vulnerability (CWE-306) exists in network-ai. Attackers reach the vulnerable code path via GET /tools.
Check the vendor advisory for the affected versions of network-ai. Attack surface: GET /tools / c344f2053eb0d49395988f803bf92f2a86b2a0d0 / config_get / agent_list.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.1.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /tools requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /tools' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /toolsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade network-ai to 5.1.3ステージング環境で 5.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /tools on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com