Advisory record · GHSA-cmwh-w62w-r2mf

Spring AI vector store metadata filtering to handle special characters in Elasticsearch, OpenSearch, and GemFire Vector Stores

CVSS 8.6 HighEPSS 0.0030 · 23rd percentile

Published by the GitHub Advisory Database at 15 Jun 2026, 21:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.springframework.ai:spring-ai-opensearch-storeMaven>=1.0.0, <1.0.9 || >=1.1.0, <1.1.81.0.9, 1.1.8
org.springframework.ai:spring-ai-elasticsearch-storeMaven>=1.0.0, <1.0.9 || >=1.1.0, <1.1.81.0.9, 1.1.8
org.springframework.ai:spring-ai-gemfire-storeMaven>=1.0.0, <1.0.9 || >=1.1.0, <1.1.81.0.9, 1.1.8
Identifiers
GHSA-cmwh-w62w-r2mf · CVE-2026-47835
Weakness (CWE)
CWE-943
Published
15 Jun 2026
Updated
26 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The spring-ai-elasticsearch-store, spring-ai-opensearch-store, and spring-ai-gemfire-store packages are affected in versions 1.0.0 through 1.0.8 and 1.1.0 through 1.1.7. Special characters can be used to force execution of arbitrary queries in the backing Elasticsearch, OpenSearch, or GemFire VectorDB store. The source gives few details on the access an attacker needs. Upgrade to 1.0.9 or 1.1.8.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.6 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L CNA (vmware)
  • CISA KEV Not listed.
  • EPSS 0.0030, the 23rd percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.