Network-AI before 5.15.5 Path Traversal via InputSanitizer.sanitizePath
Only applications that call InputSanitizer.sanitizePath() from the network-ai/security export are affected, in Network-AI 5.15.4 and earlier. Fixed in 5.15.5.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.15.5
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 31/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Fix
- Fixed in 5.15.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Network-AI, a multi-agent AI orchestration framework, is affected by a path traversal flaw in its input sanitization routine for file paths. An attacker could read, list, or write files outside the intended sandboxed directory, potentially exposing or altering sensitive data on the host system.
Read the original description
Network-AI before 5.15.5 contains a path traversal vulnerability in InputSanitizer.sanitizePath() that allows attackers to escape the base directory using sibling-directory paths. Attackers can supply paths whose directory name shares a string prefix with the base, bypassing the unanchored startsWith check to read, list, or write files outside the sandbox.
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 5.15.5.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Jovancoding Network-AI
fixed in 5.15.5
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120313
What does this mean?
sanitizePath() can let a supplied path that names a sibling directory sharing a string prefix with the base directory get outside that base directory. An attacker could then read, list, or write files the sandbox was meant to withhold.Source: github.com, vulncheck.com
Am I affected, and how do I check?
Network-AI 5.15.4 and earlier, in applications that import InputSanitizer from the published network-ai/security subpath export and call sanitizePath(). To check, look at the installed Network-AI version and search the application code for InputSanitizer imports from network-ai/security.Source: github.com, vulncheck.com
What should I do about it?
Upgrade Network-AI to 5.15.5 or later, which is the fixed version. The facts list no workaround.Source: github.com, vulncheck.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data