Quick answers
- Is CVE-2026-120312 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120312 being exploited in the wild.
- How severe is CVE-2026-120312?
- High severity, with a CVSS score of 8.8, published 2 November 2026.
- Which products and versions are affected?
- Jovancoding Network-AI 5.13.4 to 5.15.4.
- Is there a fix for CVE-2026-120312?
- Yes: fixed in 5.15.5. Until then: Restrict the cassette name input to an allowlist of safe characters (e.g., alphanumeric and underscore only) before passing it to AgentVCR.load() or AgentVCR.save(). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120312 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120312?
- Check whether you run Jovancoding Network-AI 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
- Fixed in: 5.15.5
Restrict the cassette name input to an allowlist of safe characters (e.g., alphanumeric and underscore only) before passing it to AgentVCR.load() or AgentVCR.save().
Technical details
AgentVCR.load() and AgentVCR.save() methods construct file paths by joining a configured base directory with an attacker-controlled cassette name and a .json suffix, without validating that the resolved path stays within the base directory. An attacker can use relative path traversal sequences (e.g., ../../config/secret.json) to read arbitrary .json files via load() or write/overwrite them via save(), limited only by the process's filesystem permissions and the .json extension requirement. The vulnerability stems from missing path normalization and containment checks before filesystem operations.
Affected products
- Jovancoding Network-AI 5.13.4 to 5.15.4
Timeline
- 2026-10-17: disclosed
- 2026-11-02: advisory