CVE-2026-41712 is a high-severity (CVSS 7.5) Incorrect Default Permissions vulnerability in org.springframework.ai:spring-ai-client-chat. A fix is available for org.springframework.ai:spring-ai-client-chat — see the affected versions and patch details below.
ChatMemory DEFAULT_CONVERSATION_ID causes unintended cross-user data leakage
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41712.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.ai:spring-ai-client-chat☕org.springframework.ai:spring-ai-client-chat☕org.springframework.ai:spring-ai-client-chat☕org.springframework.ai:spring-ai-model☕org.springframework.ai:spring-ai-model☕org.springframework.ai:spring-ai-model☕org.springframework.ai:spring-ai-advisors-vector-store☕org.springframework.ai:spring-ai-advisors-vector-store+1 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Spring AI's chat memory component contained a problematic default that, when not explicitly overridden, could result in unintended data exposure between users.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.ai:spring-ai-client-chat | all versions | 1.0.7org.springframework.ai:spring-ai-client-chat:1.0.7 |
| ☕Maven | org.springframework.ai:spring-ai-client-chat | ≥ 1.1.0-M1&&< 1.1.6 | 1.1.6org.springframework.ai:spring-ai-client-chat:1.1.6 |
| ☕Maven | org.springframework.ai:spring-ai-client-chat | ≥ 2.0.0-M1&&< 2.0.0-M6 | 2.0.0-M6org.springframework.ai:spring-ai-client-chat:2.0.0-M6 |
| ☕Maven | org.springframework.ai:spring-ai-model | all versions | 1.0.7org.springframework.ai:spring-ai-model:1.0.7 |
| ☕Maven | org.springframework.ai:spring-ai-model | ≥ 1.1.0-M1&&< 1.1.6 | 1.1.6org.springframework.ai:spring-ai-model:1.1.6 |
| ☕Maven | org.springframework.ai:spring-ai-model | ≥ 2.0.0-M1&&< 2.0.0-M6 | 2.0.0-M6org.springframework.ai:spring-ai-model:2.0.0-M6 |
Affected Products
spring aivmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.ai:spring-ai-client-chat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.ai:spring-ai-client-chat to 1.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41712 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2026-41712 in your dependencies?
Find it across Maven, including transitive dependencies.