Quick answers
- Is CVE-2026-58414 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58414 being exploited in the wild.
- How severe is CVE-2026-58414?
- Medium severity, with a CVSS score of 5.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-58414?
- 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-58414 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-58414?
- 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 symlink following vulnerability exists in the `EnvironmentManager.backup()` function of Network-AI. The `_collectBackupFiles()` helper function utilized `statSync()`, which resolves symbolic links, rather than `lstatSync()`. By placing a malicious symlink within the environment data directory (`data/<env>`), a local attacker with low privileges can cause the backup process to traverse the link and copy arbitrary readable files from the host system into the backup artifact directory. This issue is fixed in version 5.12.2 by switching to `lstatSync()` and explicitly skipping entries where `isSymbolicLink()` is true.
Affected products
- Jovancoding Network-AI < 5.12.2
Identifiers
- CVE-2026-58414
- GHSA-6x2m-p4xp-wg22
Timeline
- 2026-06-18: patched: Fixed in version 5.12.2 via commit a59c13a
- 2026-07-20: advisory: GHSA-6x2m-p4xp-wg22 published
- 2026-07-20: disclosed