CVE-2026-47835 is a high-severity (CVSS 8.6) CWE-943 vulnerability in org.springframework.ai:spring-ai-opensearch-store. A fix is available for org.springframework.ai:spring-ai-opensearch-store — see the affected versions and patch details below.
Spring AI vector store metadata filtering to handle special characters in Elasticsearch, OpenSearch, and GemFire Vector Stores
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-47835.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-47835 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.ai:spring-ai-opensearch-store☕org.springframework.ai:spring-ai-opensearch-store☕org.springframework.ai:spring-ai-elasticsearch-store☕org.springframework.ai:spring-ai-elasticsearch-store☕org.springframework.ai:spring-ai-gemfire-store☕org.springframework.ai:spring-ai-gemfire-storeReal-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
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).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.ai:spring-ai-opensearch-store | ≥ 1.0.0&&< 1.0.9 | 1.0.9org.springframework.ai:spring-ai-opensearch-store:1.0.9 |
| ☕Maven | org.springframework.ai:spring-ai-opensearch-store | ≥ 1.1.0&&< 1.1.8 | 1.1.8org.springframework.ai:spring-ai-opensearch-store:1.1.8 |
| ☕Maven | org.springframework.ai:spring-ai-elasticsearch-store | ≥ 1.0.0&&< 1.0.9 | 1.0.9org.springframework.ai:spring-ai-elasticsearch-store:1.0.9 |
| ☕Maven | org.springframework.ai:spring-ai-elasticsearch-store | ≥ 1.1.0&&< 1.1.8 | 1.1.8org.springframework.ai:spring-ai-elasticsearch-store:1.1.8 |
| ☕Maven | org.springframework.ai:spring-ai-gemfire-store | ≥ 1.0.0&&< 1.0.9 | 1.0.9org.springframework.ai:spring-ai-gemfire-store:1.0.9 |
| ☕Maven | org.springframework.ai:spring-ai-gemfire-store | ≥ 1.1.0&&< 1.1.8 | 1.1.8org.springframework.ai:spring-ai-gemfire-store:1.1.8 |
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-opensearch-store, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.ai:spring-ai-opensearch-store to 1.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-47835 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2026-47835 in your dependencies?
Find it across Maven, including transitive dependencies.