dbcve.org
Spring AiFramework / library · VMware

CVE-2026-47835

HIGH · 7.5 CVSS v3.1 Published 2026-06-15
Fix available
A fix is available. Upgrade to 1.0.9 / 1.1.8 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a query injection vulnerability in Spring AI Vector Store implementations (Elasticsearch, OpenSearch, and GemFire). Attackers can use special characters within vector store queries to bypass intended query boundaries and execute arbitrary queries against the underlying database, potentially exposing or manipulating unauthorized data.

MitigationUpgrade Spring AI to version 1.0.9 or 1.1.8 or later to obtain the fix. As an interim measure, implement strict input validation and sanitization of special characters in all vector store query operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring AiFramework / library
Affected:>= 1.0.0, < 1.0.9>= 1.1.0, < 1.1.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring AI version in use
    Examine your project's dependency manifest (Maven pom.xml, Gradle build.gradle, or similar) for the spring-ai-core or spring-ai dependency version. Also check any runtime classpath or container image dependency listings.
    Affected if The version is 1.0.0 through 1.0.8, or 1.1.0 through 1.1.7
  2. Determine if Elasticsearch Vector Store is in use
    Search project configuration and dependency files for spring-ai-elasticsearch-store or related Elasticsearch vector store dependencies. Review application configuration for vector store bean definitions connecting to Elasticsearch.
    Affected if Elasticsearch vector store is configured and the Spring AI version falls in the affected ranges
  3. Determine if OpenSearch Vector Store is in use
    Search project configuration and dependency files for spring-ai-opensearch-store or related OpenSearch vector store dependencies. Review application configuration for vector store bean definitions connecting to OpenSearch.
    Affected if OpenSearch vector store is configured and the Spring AI version falls in the affected ranges
  4. Determine if GemFire Vector Store is in use
    Search project configuration and dependency files for spring-ai-gemfire-store or related GemFire vector store dependencies. Review application configuration for vector store bean definitions connecting to GemFire.
    Affected if GemFire vector store is configured and the Spring AI version falls in the affected ranges
  5. Verify query operations are performed on vector stores
    Review application code for calls to vector store query methods such as 'similaritySearch', 'query', or similar VectorStore operations. Inspect logs or tracing for vector query execution patterns.
    Affected if The application executes vector store queries using the affected Spring AI versions

You are affected if your application runs Spring AI version 1.0.0-1.0.8 or 1.1.0-1.1.7 AND uses Elasticsearch, OpenSearch, or GemFire vector stores to perform query operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.9 / 1.1.8 or later
Fixed in 1.0.91.1.8
Interim mitigation

Upgrade Spring AI to version 1.0.9 or 1.1.8 or later to obtain the fix. As an interim measure, implement strict input validation and sanitization of special characters in all vector store query operations.

Recommended fix High confidence

Spring AI 1.0.9 or 1.1.8 (or later)

  1. Upgrade Spring AI to version 1.0.9 or later if using the 1.0.x line
  2. Alternatively, upgrade to version 1.1.8 or later if using the 1.1.x line
  3. Verify the upgrade by checking the Spring AI version in your project dependencies
  4. Test that vector store queries function correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Ai Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47835 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47835 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data