CVE-2026-59294

Analyzed Analyzed - Analysis Complete

ResourceCacheService Path Traversal in Spring AI

Publication date: 2026-08-27

Last updated on: 2026-08-31

Assigner: VMware

Description

ResourceCacheService.getCacheName() builds the on-disk filename by appending the URI fragment verbatim, without stripping path separators or .. sequences, and passes the result to new File(resourceParentFolder, newFileName) before writing the downloaded bytes there. Spring AI 2.0.0 Spring AI 1.1.0 - 1.1.8 Spring AI 1.0.9 and earlier

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-27

Last Modified

2026-08-31

Generated

2026-09-17

AI Q&A

2026-08-28

EPSS Evaluated

2026-09-15

NVD

CVE-2026-59294

Affected Vendors & Products

Vendor	Product	Version / Range
vmware	spring_ai	From 1.1.0 (inc) to 1.1.9 (exc)
vmware	spring_ai	to 1.0.10 (exc)
vmware	spring_ai	From 2.0.0 (inc) to 2.0.0.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-22	The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

Executive Summary

This vulnerability is an arbitrary file write issue in Spring AI's ResourceCacheService. The getCacheName() method builds filenames by appending URI fragments without sanitizing path separators or parent directory references. Attackers can exploit this by crafting URIs with path traversal sequences to write files outside the intended cache directory.

Detection Guidance

Check Spring AI application logs for suspicious file writes in cache directories. Look for filenames containing URI fragments with path traversal sequences like #/../../. Use commands such as grep -r 'ResourceCacheService' /var/log/ or find / -type f -name '*#*' 2>/dev/null to inspect files with unusual characters.

Impact Analysis

If exploited, this vulnerability could allow attackers to overwrite critical files on the system, potentially leading to code execution, configuration changes, or data corruption. The impact depends on the privileges of the running application.

Compliance Impact

This vulnerability could lead to unauthorized file modifications, potentially violating integrity requirements in GDPR and HIPAA. Unauthorized file writes may result in data breaches or tampering, triggering compliance violations and legal consequences.

Mitigation Strategies

Upgrade Spring AI to fixed versions: 2.0.1 (OSS), 2.0.0.1 (Enterprise), 1.1.9 (Enterprise), or 1.0.10 (Enterprise). Ensure applications do not accept model or tokenizer URIs from untrusted sources.

Hi! I’m here to help you understand CVE-2026-59294. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70