Is CVE-2026-47835 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47835 being exploited in the wild.

How severe is CVE-2026-47835?

High severity, with a CVSS score of 8.6, published 15 June 2026.

Which products and versions are affected?

org.springframework.ai:spring-ai-elasticsearch-store (Maven) ECOSYSTEM:introduced=1.0.0,fixed=1.0.9; org.springframework.ai:spring-ai-gemfire-store (Maven) ECOSYSTEM:introduced=1.0.0,fixed=1.0.9; org.springframework.ai:spring-ai-opensearch-store (Maven) ECOSYSTEM:introduced=1.0.0,fixed=1.0.9; VMware Spring Ai 1.0.0 through 1.0.x (fix 1.1.9), 1.1.0 through 1.1.x (fix 1.1.8); and 3 more.

Is there a fix for CVE-2026-47835?

Yes. org.springframework.ai:spring-ai-elasticsearch-store (Maven): upgrade to 1.0.9 or later; org.springframework.ai:spring-ai-gemfire-store (Maven): upgrade to 1.0.9 or later; org.springframework.ai:spring-ai-opensearch-store (Maven): upgrade to 1.0.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-47835 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-47835?

Check whether you run org.springframework.ai:spring-ai-elasticsearch-store (Maven), org.springframework.ai:spring-ai-gemfire-store (Maven), org.springframework.ai:spring-ai-opensearch-store (Maven) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47835: VMware Spring AI query injection in Vector Stores

CVE-2026-47835 · Severity: high · CVSS 8.6 · Published 2026-06-15

Spring AI's vector store components (Elasticsearch, OpenSearch, and GemFire integrations) fail to properly escape special characters in metadata filtering queries, allowing attackers to inject arbitrary query logic. An unauthenticated remote attacker can exploit this to extract sensitive data, modify search results, or potentially access unauthorized information from the underlying vector databases.

Technologies: VMware Spring Ai. Vendors: Maven, VMware.

Quick answers

Is CVE-2026-47835 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47835 being exploited in the wild.
How severe is CVE-2026-47835?: High severity, with a CVSS score of 8.6, published 15 June 2026.
Which products and versions are affected?: org.springframework.ai:spring-ai-elasticsearch-store (Maven) ECOSYSTEM:introduced=1.0.0,fixed=1.0.9; org.springframework.ai:spring-ai-gemfire-store (Maven) ECOSYSTEM:introduced=1.0.0,fixed=1.0.9; org.springframework.ai:spring-ai-opensearch-store (Maven) ECOSYSTEM:introduced=1.0.0,fixed=1.0.9; VMware Spring Ai 1.0.0 through 1.0.x (fix 1.1.9), 1.1.0 through 1.1.x (fix 1.1.8); and 3 more.
Is there a fix for CVE-2026-47835?: Yes. org.springframework.ai:spring-ai-elasticsearch-store (Maven): upgrade to 1.0.9 or later; org.springframework.ai:spring-ai-gemfire-store (Maven): upgrade to 1.0.9 or later; org.springframework.ai:spring-ai-opensearch-store (Maven): upgrade to 1.0.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47835 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-47835?: Check whether you run org.springframework.ai:spring-ai-elasticsearch-store (Maven), org.springframework.ai:spring-ai-gemfire-store (Maven), org.springframework.ai:spring-ai-opensearch-store (Maven) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.springframework.ai:spring-ai-elasticsearch-store (Maven): upgrade to 1.0.9 or later

# set org.springframework.ai:spring-ai-elasticsearch-store to 1.0.9 in your pom.xml or build.gradle

org.springframework.ai:spring-ai-gemfire-store (Maven): upgrade to 1.0.9 or later

# set org.springframework.ai:spring-ai-gemfire-store to 1.0.9 in your pom.xml or build.gradle

org.springframework.ai:spring-ai-opensearch-store (Maven): upgrade to 1.0.9 or later

# set org.springframework.ai:spring-ai-opensearch-store to 1.0.9 in your pom.xml or build.gradle

Technical details

The vulnerability is a query injection flaw (CWE-943: Improper Neutralization of Special Elements in Data Query Logic) in Spring AI's vector store filter expression converters for Elasticsearch, OpenSearch, and GemFire. The affected components fail to properly escape tab, newline, and carriage-return characters in metadata filtering queries before passing them to the underlying vector databases. This allows an unauthenticated remote attacker to inject special characters that modify the query logic and force execution of arbitrary database queries. The vulnerability requires no user interaction and affects systems where these vector stores are exposed over a network. The fix escapes these special characters in the filter expression conversion logic. Patches are available in Spring AI 1.0.9 and 1.1.8.

Affected products

Spring spring-ai-elasticsearch-store 1.0.0 through 1.0.8, 1.1.0 through 1.1.7
Spring spring-ai-opensearch-store 1.0.0 through 1.0.8, 1.1.0 through 1.1.7
Spring spring-ai-gemfire-store 1.0.0 through 1.0.8, 1.1.0 through 1.1.7

Identifiers

CVE-2026-47835
GHSA-cmwh-w62w-r2mf

Timeline

2026-06-15: disclosed: Published by GitHub Advisory Database and NVD
2026-06-12: patched: Spring AI 1.0.9 and 1.1.8 released with fixes

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.