Path Traversal in network-ai (CVE-2026-58414)
Summary
Path traversal in network-ai (CVE-2026-58414). Confidential information can be exposed externally. Exploitable via copied. Mitigation: upgrade to 5.12.2 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.12.2, EnvironmentManager.backup() recursively collects files using _collectBackupFiles(). _collectBackupFiles() uses statSync(full), which follows symlinks. If data/ contains a symlink to a directory outside the environment root, backup recursion follows the symlink and copies external files into data//.backups//. An attacker who can place a symlink under the environment data directory can cause backup operations to disclose files outside the environment root into backup artifacts. The issue is fixed in v5.12.2. _collectBackupFiles() now uses lstatSync instead of statSync and skips any entry where isSymbolicLink() is true. Symlinks are never traversed, so backup() can no longer follow a link out of the environment root and copy external files into a backup artifact.
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-58414 has been found in network-ai.
Attackers can target a specific entry point like copied over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade network-ai to 5.12.2 or later.
If unsure, ask your IT team or search "network-ai CVE-2026-58414" on the vendor's site.
CVE-2026-58414 (network-ai) — CWE-22 / CVSS v3 5.5
Attack vector: local / no user interaction
Attack surface: copied / true / content / a59c13a
Patched: 5.12.2 — 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.
Path traversal (CWE-22) exists in network-ai. Attackers reach the vulnerable code path via copied.
Check the vendor advisory for the affected versions of network-ai. Attack surface: copied / true / content / a59c13a.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to 5.12.2.
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.12.2ステージング環境で 5.12.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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