CVE-2026-47835: CWE-943: Improper Neutralization of Special Elements in Data Query Logic in Spring Spring AI
In Spring AI Vector Stores, special characters could be used to force the execution of arbitrary queries in Elasticsearch, OpenSearch, and GemFire VectorDB. Affected components: spring-ai-elasticsearch-store, spring-ai-opensearch-store, spring-ai-gemfire-store. Affected versions: Spring AI 1.0.0 through 1.0.x (fix 1.0.9). Spring AI 1.1.0 through 1.1.x (fix 1.1.8).
AI Analysis
Technical Summary
The vulnerability identified as CVE-2026-47835 involves improper neutralization of special elements in data query logic (CWE-943) within Spring AI Vector Stores. Specifically, special characters can be used to manipulate query execution in the affected vector store components for Elasticsearch, OpenSearch, and GemFire VectorDB. This can lead to unauthorized query execution, potentially exposing or altering sensitive data. The affected versions include Spring AI 1.0.0 through 1.0.x and 1.1.0 through 1.1.x. Fixes have been released in versions 1.0.9 and 1.1.8. The CVSS v3.1 base score is 8.6, indicating a high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and high confidentiality impact with limited integrity and availability impact.
Potential Impact
Successful exploitation could allow an unauthenticated attacker to execute arbitrary queries against Elasticsearch, OpenSearch, or GemFire VectorDB through the Spring AI Vector Stores. This can lead to high confidentiality impact by exposing sensitive data, with additional limited impacts on integrity and availability. There are no known exploits in the wild currently.
Mitigation Recommendations
Fixes are available in Spring AI versions 1.0.9 and 1.1.8. Users should upgrade affected components (spring-ai-elasticsearch-store, spring-ai-opensearch-store, spring-ai-gemfire-store) to these versions or later to remediate the vulnerability. Patch status is not explicitly confirmed in the vendor advisory, but the presence of fixed versions indicates official fixes are available. No alternative mitigations are specified.
CVE-2026-47835: CWE-943: Improper Neutralization of Special Elements in Data Query Logic in Spring Spring AI
Description
In Spring AI Vector Stores, special characters could be used to force the execution of arbitrary queries in Elasticsearch, OpenSearch, and GemFire VectorDB. Affected components: spring-ai-elasticsearch-store, spring-ai-opensearch-store, spring-ai-gemfire-store. Affected versions: Spring AI 1.0.0 through 1.0.x (fix 1.0.9). Spring AI 1.1.0 through 1.1.x (fix 1.1.8).
CVSS v3.1
Score 8.6high
Affected software
pkg:maven/org.springframework.experimental/spring-ai-elasticsearch-storepkg:maven/org.springframework.experimental/spring-ai-opensearch-storepkg:maven/org.springframework.experimental/spring-ai-gemfire-storeRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability identified as CVE-2026-47835 involves improper neutralization of special elements in data query logic (CWE-943) within Spring AI Vector Stores. Specifically, special characters can be used to manipulate query execution in the affected vector store components for Elasticsearch, OpenSearch, and GemFire VectorDB. This can lead to unauthorized query execution, potentially exposing or altering sensitive data. The affected versions include Spring AI 1.0.0 through 1.0.x and 1.1.0 through 1.1.x. Fixes have been released in versions 1.0.9 and 1.1.8. The CVSS v3.1 base score is 8.6, indicating a high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and high confidentiality impact with limited integrity and availability impact.
Potential Impact
Successful exploitation could allow an unauthenticated attacker to execute arbitrary queries against Elasticsearch, OpenSearch, or GemFire VectorDB through the Spring AI Vector Stores. This can lead to high confidentiality impact by exposing sensitive data, with additional limited impacts on integrity and availability. There are no known exploits in the wild currently.
Mitigation Recommendations
Fixes are available in Spring AI versions 1.0.9 and 1.1.8. Users should upgrade affected components (spring-ai-elasticsearch-store, spring-ai-opensearch-store, spring-ai-gemfire-store) to these versions or later to remediate the vulnerability. Patch status is not explicitly confirmed in the vendor advisory, but the presence of fixed versions indicates official fixes are available. No alternative mitigations are specified.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-05-20T10:00:51.003Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3052e10b89be6888827495
Added to database: 6/15/2026, 7:30:41 PM
Last enriched: 6/15/2026, 8:00:20 PM
Last updated: 6/16/2026, 4:58:00 AM
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.