Quick answers
- Is CVE-2026-58481 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58481 being exploited in the wild.
- How severe is CVE-2026-58481?
- Medium severity, with a CVSS score of 6.5, published 20 July 2026.
- Which products and versions are affected?
- Jovancoding Network-AI < 5.12.2; network-ai (npm) SEMVER:introduced=0,fixed=5.12.2.
- Is there a fix for CVE-2026-58481?
- Yes. network-ai (npm): upgrade to 5.12.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58481 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-58481?
- Check whether you run Jovancoding Network-AI or network-ai (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- network-ai (npm): upgrade to 5.12.2 or later
npm install network-ai@5.12.2
Technical details
A path traversal vulnerability exists in Network-AI's AgentRuntime and SandboxPolicy components due to improper path validation. The software uses a raw string prefix check (startsWith) to enforce sandbox boundaries, which fails to account for directory separators. An attacker can bypass the sandbox by targeting sibling directories that share the same name prefix as the configured basePath (e.g., accessing '/tmp/sandbox_evil' when the sandbox is set to '/tmp/sandbox'). This allows local users or agents to call readFile() or listDir() to access files outside the intended scope. The issue is resolved in version 5.12.2 by implementing separator-anchored prefix checks.
Affected products
- Jovancoding Network-AI < 5.12.2
Identifiers
- CVE-2026-58481
- GHSA-jvcm-f35g-w78p
Timeline
- 2026-06-18: patched: Fixed in version 5.12.2 via commit a59c13a
- 2026-07-20: disclosed: CVE-2026-58481 published