Description
Network-AI is a TypeScript/Node.js multi-agent orchestrator. Prior to version 5.12.2, `AgentRuntime` promises scoped file access under a configured sandbox `basePath`, but its path containment checks use raw string prefix tests. A sandbox base such as `/tmp/network-ai-sandbox` also matches a sibling path such as `/tmp/network-ai-sandbox_evil/secret.txt`. An agent/user that can call `AgentRuntime.readFile()` or `AgentRuntime.listDir()` can read or list files outside the intended sandbox when the target path is in a sibling directory sharing the base path prefix. This breaks the documented sandbox boundary. The issue is fixed in v5.12.2. `SandboxPolicy.resolvePath()` and `isPathAllowed()` now use separator-anchored prefix checks (`resolved === base || resolved.startsWith(base + path.sep)`) for both the allow-list and block-list. A sibling directory that merely shares a name prefix (e.g. `/srv/app-evil` vs base `/srv/app`) is no longer treated as in-scope.
Published: 2026-07-20
Score: 6.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Network-AI’s AgentRuntime was designed to ensure file system access is confined to a user-specified sandbox directory. The containment logic, however, relied on simple string prefix comparisons, which allowed paths such as "/tmp/network-ai-sandbox_evil/secret.txt" to satisfy the check for the base path "/tmp/network-ai-sandbox". This flaw means that any agent or user able to invoke AgentRuntime.readFile() or AgentRuntime.listDir() can read or enumerate files outside the intended sandbox, exposing sensitive data residing in adjacent directories. The weakness is a typical path-traversal issue, represented by CWE-22 and CWE-23.

Affected Systems

The vulnerability affects the Jovancoding Network-AI orchestrator in all releases prior to version 5.12.2. The fix was introduced in v5.12.2, where SandboxPolicy.resolvePath() and isPathAllowed() now enforce separator-anchored prefix checks to validate that resolved paths are equal to or descend from the configured base.

Risk and Exploitability

With a CVSS score of 6.5, the issue is classified as medium severity. The EPSS score of less than 1% indicates a very low probability of exploitation. The vulnerability is not listed in CISA’s KEV catalog. Exploitation requires an attacker to supply a file path that shares the same base prefix but points to a sibling directory, and to have the ability to call AgentRuntime.readFile() or listDir(). No elevated system privileges are required, so the risk is confined to scenarios where the attacker can influence the API arguments or otherwise invoke these file-access methods.

Generated by OpenCVE AI on July 30, 2026 at 19:01 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Jovancoding Network-AI to version 5.12.2 or newer to receive the fixed separator-anchored path checks.
  • If an upgrade is not possible, implement a custom validation layer that verifies the resolved path is exactly the configured base or a descendant of it before passing it to the file-access APIs.
  • Restrict the privileges of the AgentRuntime instance and ensure that only trusted agents or users have permission to invoke read or list operations.

Generated by OpenCVE AI on July 30, 2026 at 19:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 20 Jul 2026 23:30:00 +0000

Type Values Removed Values Added
First Time appeared Jovancoding
Jovancoding network-ai
Vendors & Products Jovancoding
Jovancoding network-ai

Mon, 20 Jul 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 20 Jul 2026 16:45:00 +0000

Type Values Removed Values Added
Description Network-AI is a TypeScript/Node.js multi-agent orchestrator. Prior to version 5.12.2, `AgentRuntime` promises scoped file access under a configured sandbox `basePath`, but its path containment checks use raw string prefix tests. A sandbox base such as `/tmp/network-ai-sandbox` also matches a sibling path such as `/tmp/network-ai-sandbox_evil/secret.txt`. An agent/user that can call `AgentRuntime.readFile()` or `AgentRuntime.listDir()` can read or list files outside the intended sandbox when the target path is in a sibling directory sharing the base path prefix. This breaks the documented sandbox boundary. The issue is fixed in v5.12.2. `SandboxPolicy.resolvePath()` and `isPathAllowed()` now use separator-anchored prefix checks (`resolved === base || resolved.startsWith(base + path.sep)`) for both the allow-list and block-list. A sibling directory that merely shares a name prefix (e.g. `/srv/app-evil` vs base `/srv/app`) is no longer treated as in-scope.
Title Network-AI: AgentRuntime sandbox path-prefix checks allow file access outside the configured base directory
Weaknesses CWE-22
CWE-23
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N'}


Subscriptions

Jovancoding Network-ai
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-20T17:42:43.376Z

Reserved: 2026-06-30T20:21:25.811Z

Link: CVE-2026-58481

cve-icon Vulnrichment

Updated: 2026-07-20T17:42:35.196Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-30T19:15:04Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-23

    Relative Path Traversal