Skip to main content

Spring AI CVE-2026-41712

| EUVDEUVD-2026-29448 HIGH
Incorrect Default Permissions (CWE-276)
2026-05-12 vmware GHSA-q62f-h9x2-gcqc
7.5
CVSS 3.1 · Vendor: vmware
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Access network-accessible Spring AI endpoint
  2. Exploit
    Send chat requests during concurrent user activity
  3. Execution
    Receive leaked memory containing other users' data
  4. Impact
    Extract confidential information from responses

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Default permission hardening
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No special conditions - remote unauthenticated exploitation against default configurations of Spring AI applications utilizing the chat memory component. Exploitation is most effective in multi-user or multi-tenant environments where concurrent users interact with the same Spring AI instance. However, the vulnerability is limited to applications that have not explicitly configured chat memory isolation and rely on the framework's default settings. Single-user or properly isolated implementations where developers have overridden default chat memory configuration are not vulnerable. The network attack vector (AV:N) means the application must be network-accessible, but no special network position, user interaction (UI:N), or authentication (PR:N) is required.

Impact

This vulnerability presents significant real-world risk for production Spring AI applications handling multiple users. The CVSS 7.5 (High) score accurately reflects the severity: network-accessible (AV:N), low complexity exploitation (AC:L), no authentication required (PR:N), and high confidentiality impact (C:H). An attacker needs only network access to a vulnerable Spring AI application to potentially view other users' chat histories, prompts, and AI responses. The attack complexity is low because exploitation likely requires simple timing manipulation or session enumeration rather than sophisticated techniques. The scope is unchanged (S:U), meaning the vulnerability is contained within Spring AI's security context, but the confidentiality breach can expose sensitive business data, personal information, or proprietary prompts shared with AI systems. No EPSS, KEV, or POC data is available in the provided intelligence, suggesting either recent disclosure or limited public visibility. The Java ecosystem tag indicates this affects enterprise environments where Spring AI may process confidential corporate communications or customer data. Priority should be HIGH for any organization running Spring AI in production with multiple users, as the unauthenticated network vector and high confidentiality impact create immediate data breach risk. The absence of integrity or availability impact (I:N/A:N) means this is strictly an information disclosure vulnerability, not allowing system compromise or service disruption.

Exploit ScenarioDerived

An attacker accesses a Spring AI-powered chatbot application used by multiple customers of an enterprise. Without authentication or by using a valid but low-privilege account, the attacker crafts requests to the chat endpoint while monitoring timing or session identifiers. Due to the default shared memory configuration, the attacker's chat session intermittently receives responses containing fragments of other users' conversations, exposing confidential customer queries, business data, or personal information previously submitted to the AI system. The attacker systematically collects this leaked data by repeatedly initiating chat sessions during periods of concurrent user activity.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 12, 2026

Remote unauthenticated attackers can access confidential data from other users' chat sessions in Spring AI applications due to insecure default configuration in the chat memory component. The vulnerability allows network-based exploitation with no authentication required (CVSS:3.1 AV:N/AC:L/PR:N/UI:N) and impacts confidentiality only (C:H/I:N/A:N), enabling cross-user data leakage in multi-tenant AI chat implementations. Reported by VMware, affecting Java-based Spring AI deployments where developers have not explicitly configured chat memory isolation.

RemediationAI

Upgrade to the patched version of Spring AI specified in VMware's security advisory at https://spring.io/security/cve-2026-41712, which addresses the insecure default in the chat memory component. If immediate patching is not feasible, implement explicit chat memory isolation by configuring session-scoped memory instances per user with proper access controls. Developers should override the default chat memory configuration to use user-specific memory contexts, ensuring each user session maintains isolated conversation history. This can typically be achieved by binding chat memory instances to authenticated user sessions and implementing session validation before memory access. Review application code to ensure chat memory components are initialized with user-scoped isolation rather than shared global state. For applications where chat memory functionality is not essential, consider disabling the feature entirely until patching is complete. Note that workaround implementations may impact performance in high-concurrency scenarios due to increased memory overhead from per-user isolation.

Affected VersionsENISA

Spring AI 1.1.0 <1.1.6
Spring AI 1.0.0 <1.0.7

Affected Packages

maven org.springframework.ai:spring-ai-advisors-vector-store fix: 1.0.7, 1.1.6, 2.0.0-M6
maven org.springframework.ai:spring-ai-client-chat fix: 1.0.7, 1.1.6, 2.0.0-M6
maven org.springframework.ai:spring-ai-model fix: 1.0.7, 1.1.6, 2.0.0-M6
euvd spring_ai fix: 1.0.7, 1.1.6

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in maven, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Spring AI is VMware's framework for building AI-powered applications in Java ecosystems. The vulnerability resides in the chat memory component, which maintains conversation state and context for AI interactions. Chat memory components typically store user prompts, AI responses, and session context to enable coherent multi-turn conversations. The problematic default configuration fails to implement proper isolation boundaries between user sessions, allowing one user's memory context to leak into another's. This affects applications built on the Spring AI framework (CPE: cpe:2.3:a:vmware:spring_ai) where developers rely on default chat memory settings rather than explicitly configuring session isolation mechanisms. The issue represents a classic framework security misconfiguration where secure-by-default principles were not applied to a multi-user feature.

Know when Spring Ai gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vmware) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from Vendor (vmware) · only source for this CVE.

CVSS VectorVendor: vmware

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch available
May 12, 2026 - 12:02 EUVD
CVE Published
May 12, 2026 - 10:17 nvd
HIGH 7.5

DescriptionCVE.org

Spring AI's chat memory component contained a problematic default that, when not explicitly overridden, could result in unintended data exposure between users.

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 37 maven packages depend on org.springframework.ai:spring-ai-client-chat (6 direct, 31 indirect)

Ecosystem-wide dependent count for version 1.1.0-M1.

Executive ViewAI

Why It Matters

Spring AI chat memory components contain an insecure default configuration that allows unauthenticated remote attackers to access other users' confidential chat session data across multi-tenant deployments. This cross-user data leakage vulnerability puts customer privacy and compliance obligations at immediate risk for any organization running Spring AI chat applications without explicit memory isolation controls.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Implement application-level chat memory isolation by explicitly configuring per-user/per-tenant storage separation in Spring AI configuration; (2) restrict network access to Spring AI services via network segmentation or WAF rules; (3) enable audit logging on all chat memory access and monitor for cross-tenant data requests; (4) implement request-level authorization checks before returning any chat session data; (5) isolate multi-tenant deployments into separate application instances or containers per tenant pending patch release.

Threat Intelligence Overview

EPSS Score
0.0%
Top 89% exploitable
Threat Intel
1
1 source
Social Media
4
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2026-59318 CRITICAL
9.8 Aug 21

Incorrect authorization in Spring AI's tool-calling layer allows a tool that was never advertised to the current request

CVE-2026-22738 CRITICAL
9.8 Mar 27

Spring AI versions 1.0.0 through 1.0.4 and 1.1.0 through 1.1.3 allow unauthenticated remote code execution through Sprin

CVE-2026-40978 HIGH
8.8 Apr 28

SQL injection in Spring AI's CosmosDBVectorStore component (versions 1.0.0-1.0.5 and 1.1.0-1.1.4) enables authenticated

CVE-2026-22730 HIGH
8.8 Mar 18

A critical SQL injection vulnerability in Spring AI's MariaDBFilterExpressionConverter component allows authenticated at

CVE-2026-22729 HIGH
8.6 Mar 18

Spring AI's AbstractFilterExpressionConverter fails to properly escape user-controlled input in JSONPath queries, allowi

CVE-2026-40967 HIGH
8.6 Apr 28

Filter expression injection in Spring AI 1.0.0-1.0.5 and 1.1.0-1.1.4 allows remote unauthenticated attackers to manipula

CVE-2026-22742 HIGH
8.6 Mar 27

Server-Side Request Forgery in Spring AI Bedrock Converse module enables unauthenticated remote attackers to force the a

CVE-2026-41705 HIGH
8.6 May 09

Filter-expression injection in Spring AI's MilvusVectorStore allows remote unauthenticated attackers to manipulate vecto

CVE-2026-41713 HIGH
8.2 May 12

Conversation memory poisoning in VMware Spring AI allows remote unauthenticated attackers to inject malicious input that

CVE-2026-47835 HIGH
7.5 Jun 15

Query injection in the Spring AI vector-store modules - spring-ai-elasticsearch-store, spring-ai-opensearch-store and sp

CVE-2026-59279 HIGH
7.5 Aug 21

Unbounded session accumulation in Spring AI 2.0.0's MCP Streamable HTTP server transport enables remote unauthenticated

CVE-2026-47851 HIGH
7.5 Aug 26

Denial of service in Spring AI's PDF document ingestion crashes the processing thread when parsing a crafted PDF with a

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy