CVE-2026-41863 json
LLM-influenced filename used unsanitized in Path.resolve before file write in Spring AI support for Anthropic Skills API
published 5mo ago modified 3mo ago also GHSA-cc4m-mp48-x7qg , EUVD-2026-31638
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
Spring AI's support for Anthropic's Skills API used LLM-influenced filenames unsanitized in Path.resolve before writing files to disk. This could allow a malicious user to write files outside the intended target directory, including restricted directories.
Affected versions: Spring AI: 1.1.0 through 1.1.x
Patch / fix
- maven org.springframework.ai:spring-ai-anthropic 1.1.7
- vmware spring_ai 1.1.7
Is CVE-2026-41863 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5mo ago
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.ai:spring-ai-anthropic | >=1.1.0, <1.1.7 |
1.1.7 |
Affected products
- Spring Spring AI
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
spring.io
/security/cve-2026-41863
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-41863
advisory
-
github.com
/spring-projects/spring-ai
package
Sources
- CVE List CVE-2026-41863
- GitHub Advisory GHSA-cc4m-mp48-x7qg
- NVD CVE-2026-41863
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.