Spring AiFramework / library · VMware
CVE-2026-41863
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSpring 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSpring AI's Anthropic Skills API integration uses filenames influenced by LLM output directly in Path.resolve() without sanitization, allowing path traversal attacks where malicious filenames like '../../../etc/passwd' can write files outside the intended directory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Spring AiFramework / library
>= 1.1.0, < 1.1.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Spring AI version in your deploymentCheck your project's dependency file (pom.xml or build.gradle) for the spring-ai-core or spring-ai-anthropic version, or inspect the deployed JAR/WAR file's manifest. In Maven, run: mvn dependency:tree | grep spring-aiAffected if The installed Spring AI version is >= 1.1.0 and < 1.1.7
-
Confirm Anthropic Skills API integration is in useSearch your codebase for imports of classes from org.springframework.ai.anthropic or usage of AnthropicChatModel, AnthropicSkill, or similar Anthropic-related beans in your Java configuration or Spring context filesAffected if Your application uses the Anthropic integration for Skills functionality
-
Locate file write operations using LLM-provided filenamesSearch your codebase for Path.resolve() calls or File/Path operations where the filename argument originates from LLM output, anthropic responses, or skill execution resultsAffected if Your code passes LLM-generated filenames directly to Path.resolve or similar file operations without sanitization
-
Inspect input validation on filename parametersReview any validation logic that processes filenames before file operations. Check for rejection of '..' sequences, absolute paths (starting with / or \), or other path traversal patternsAffected if No validation exists, or validation can be bypassed by the LLM-generated input
You are affected if Spring AI version is between 1.1.0 and 1.1.7 inclusive, and your application uses Anthropic Skills that pass LLM-generated filenames to file operations without sanitizing path traversal sequences.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.1.7
Implement strict filename validation and path traversal checks - validate that resolved paths remain within the intended target directory using canonical path comparisons before file operations.
Spring AI 1.1.7
- Update the Spring AI dependency version in your project's build configuration (pom.xml for Maven or build.gradle for Gradle) from the current 1.1.x version to 1.1.7
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Ai
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41863 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41863 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data