CVE-2026-58481: Network-AI: AgentRuntime sandbox path-prefix checks allow file access outside the configured base directory

Published Jul 20, 2026
·
Updated

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

Affected Software

2 affected components
Network-AI AgentRuntime<5.12.2
Network-AI Network-AI<5.12.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Network-AI (AgentRuntime) to a version that resolves this vulnerability.

    Fixed in 5.12.2
  2. Configuration

    In SandboxPolicy.resolvePath() and isPathAllowed(), replace raw string prefix tests with separator-anchored prefix checks: resolved === base OR resolved.startsWith(base + path.sep) for both allow-list and block-list so sibling paths sharing the base path prefix (e.g., /srv/app-evil vs base /srv/app) are not treated as in-scope.

    Network-AI SandboxPolicy isPathAllowed / resolvePath path containment checks = separator-anchored allow/block prefix checks using resolved === base OR resolved.startsWith(base + path.sep)

Event History

Jul 20, 2026
CVE Published
via MITRE·04:30 PM
Data Sourced
via MITRE·04:30 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:18 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-58481?

The severity of CVE-2026-58481 is rated as medium with a score of 6.5.

2

How do I fix CVE-2026-58481?

To mitigate CVE-2026-58481, upgrade to Network-AI AgentRuntime version 5.12.2 or later.

3

What type of vulnerability is CVE-2026-58481?

CVE-2026-58481 is classified as a Path Traversal vulnerability.

4

What does CVE-2026-58481 affect?

CVE-2026-58481 affects the Network-AI AgentRuntime prior to version 5.12.2.

5

What are the impact details of CVE-2026-58481?

CVE-2026-58481 allows file access outside the configured base directory due to insufficient path containment checks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203