Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5amended

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

CVE-2026-58481GHSA-jvcm-f35g-w78p

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (network-ai 5.12.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
  • CVE-2026-58481: 0.19% estimated exploitation activity in the next 30 days; percentile 8.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. Confirmed in Network-AI 5.12.1. Severity: Medium, CVSS 3.1 vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. Details The vulnerable containment check is in lib/agent-runtime.ts: startsWith() is not path-boundary-aware. If this.config.basePath is /tmp/network-ai-sandbox, then /tmp/network-ai-sandboxevil/secret.txt also starts with /tmp/network-ai-sandbox despite being outside the sandbox. The same pattern appears in SandboxPolicy.isPathAllowed() for allowed and blocked…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-jvcm-f35g-w78p

  2. Revision 1 · created ·

    Published from osv record GHSA-jvcm-f35g-w78p

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-58481

Advisory: Network-AI: AgentRuntime sandbox path-prefix checks allow file access outside the configured base directory
IDs: CVE-2026-58481, GHSA-jvcm-f35g-w78p
Record: https://patchnext.com/advisories/cve-2026-58481 (revision 2, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: network-ai 5.12.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm network-ai: affected <= 5.12.1; fixed in 5.12.2

## Suggested inspection (read-only)
- `npm ls network-ai --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on network-ai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jvcm-f35g-w78p (OSV record GHSA-jvcm-f35g-w78p lists affected ranges: npm network-ai >=0 <5.12.2 (fixed))
- Verified: https://github.com/advisories/GHSA-jvcm-f35g-w78p (GitHub-reviewed advisory GHSA-jvcm-f35g-w78p lists affected ranges: npm network-ai >=0 <=5.12.1)

Commands are suggestions: review each one before running it.

Loading voting…