Quick answers
- Is CVE-2026-59294 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59294 being exploited in the wild.
- How severe is CVE-2026-59294?
- Medium severity, with a CVSS score of 5.9, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring Ai 1.0.9 and earlier, 1.1.0–1.1.8, 2.0.0.
- Is there a fix for CVE-2026-59294?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-59294 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-59294?
- Check whether you run VMware Spring 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.
Technical details
The vulnerability exists in ResourceCacheService.getCacheName(), which constructs on-disk filenames by concatenating a resource parent folder path with a URI fragment without sanitizing path separators or ".." sequences. This unsanitized filename is then passed to the File constructor before writing downloaded content, enabling path traversal attacks. An attacker can craft a malicious URI with fragments like "../../sensitive/file.txt" to write arbitrary content outside the intended cache directory. The vulnerability requires network access to trigger the download, but no authentication is required. Patched versions should sanitize URI fragments by removing or escaping path traversal sequences.
Affected products
- VMware Spring AI 1.0.9 and earlier, 1.1.0–1.1.8, 2.0.0
Timeline
- 2026-08-27: disclosed