VulnerabilityPublished 15 Jun 2026

CVE-2026-47835: Spring AI · Improper Neutralization of Special Elements in Data Query Logic

Affects Spring AISource CVE Database V5

Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 1.1.8 or 1.0.9 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.1.8, 1.0.9

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Spring AI and org.springframework.experimental/spring-ai-elasticsearch-store and org.springframework.experimental/spring-ai-opensearch-store and org.springframework.experimental/spring-ai-gemfire-store to 1.1.8 or 1.0.9.

Affected software

Product	Affected	Fixed in
SpringSpring AI	Affected >=1.1.0 <1.1.8	Fixed in 1.1.8
SpringSpring AI	Affected >=1.0.0 <1.0.9	Fixed in 1.0.9
Mavenorg.springframework.experimental/spring-ai-elasticsearch-store`pkg:maven/org.springframework.experimental/spring-ai-elasticsearch-store`Other threats	Affected >=1.0.0 <1.0.9 >=1.1.0 <1.1.8 =1.0.0 =1.1.0	Fixed in 1.0.9 1.1.8
Mavenorg.springframework.experimental/spring-ai-opensearch-store`pkg:maven/org.springframework.experimental/spring-ai-opensearch-store`Other threats	Affected >=1.0.0 <1.0.9 >=1.1.0 <1.1.8 =1.0.0 =1.1.0	Fixed in 1.0.9 1.1.8
Mavenorg.springframework.experimental/spring-ai-gemfire-store`pkg:maven/org.springframework.experimental/spring-ai-gemfire-store`Other threats	Affected >=1.0.0 <1.0.9 >=1.1.0 <1.1.8 =1.0.0 =1.1.0	Fixed in 1.0.9 1.1.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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).

CWE-943Improper Neutralization of Special Elements in Data Query Logic (opens in a new tab)
Class weakness
The product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
NoSQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

spring.io/security/cve-2026-47835 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Jun 2026, 20:00 UTC

WeaknessesCWE-943

Technical details

References

Community reviews

Related threats