How severe is CVE-2026-22729?

CVE-2026-22729 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.springframework.ai:spring-ai-vector-store are affected by CVE-2026-22729?

org.springframework.ai:spring-ai-vector-store (maven) versions >= 1.1.0-M1, < 1.1.3 is affected.

Is there a fix for CVE-2026-22729?

Yes. CVE-2026-22729 is fixed in 1.1.3, 1.0.4. Upgrade to this version or later.

Is CVE-2026-22729 exploitable, and should I be worried?

Whether CVE-2026-22729 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-22729 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-22729 in org.springframework.ai:spring-ai-vector-store | Intelligent Application Security

Q: What is CVE-2026-22729?

CVE-2026-22729 is a high-severity security vulnerability in org.springframework.ai:spring-ai-vector-store (maven), affecting versions >= 1.1.0-M1, < 1.1.3. It is fixed in 1.1.3, 1.0.4.

Q: Is there a fix for CVE-2026-22729?

Yes. CVE-2026-22729 is fixed in 1.1.3, 1.0.4. Upgrade to this version or later.

Q: Is CVE-2026-22729 exploitable, and should I be worried?

Whether CVE-2026-22729 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-22729 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-22729?

Upgrade: org.springframework.ai:spring-ai-vector-store to 1.1.3 or later, org.springframework.ai:spring-ai-vector-store to 1.0.4 or later.

Summary

A JSONPath injection vulnerability in Spring AI's AbstractFilterExpressionConverter allows authenticated users to bypass metadata-based access controls through crafted filter expressions. User-controlled input passed to FilterExpressionBuilder is concatenated into JSONPath queries without proper escaping, enabling attackers to inject arbitrary JSONPath logic and access unauthorized documents.

This vulnerability affects applications using vector stores that extend AbstractFilterExpressionConverter for multi-tenant isolation, role-based access control, or document filtering based on metadata.

The vulnerability occurs when user-supplied values in filter expressions are not escaped before being inserted into JSONPath queries. Special characters like ", ||, and && are passed through unescaped, allowing injection of arbitrary JSONPath logic that can alter the intended query semantics.

Impact

CVE-2026-22729 has a CVSS score of 8.6 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.1.3, 1.0.4); upgrading removes the vulnerable code path.

Affected versions

org.springframework.ai:spring-ai-vector-store (>= 1.1.0-M1, < 1.1.3) org.springframework.ai:spring-ai-vector-store (< 1.0.4)

Security releases

org.springframework.ai:spring-ai-vector-store → 1.1.3 (maven) org.springframework.ai:spring-ai-vector-store → 1.0.4 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.springframework.ai:spring-ai-vector-store to 1.1.3 or later; org.springframework.ai:spring-ai-vector-store to 1.0.4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-22729? CVE-2026-22729 is a high-severity security vulnerability in org.springframework.ai:spring-ai-vector-store (maven), affecting versions >= 1.1.0-M1, < 1.1.3. It is fixed in 1.1.3, 1.0.4.
How severe is CVE-2026-22729? CVE-2026-22729 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.springframework.ai:spring-ai-vector-store are affected by CVE-2026-22729? org.springframework.ai:spring-ai-vector-store (maven) versions >= 1.1.0-M1, < 1.1.3 is affected.
Is there a fix for CVE-2026-22729? Yes. CVE-2026-22729 is fixed in 1.1.3, 1.0.4. Upgrade to this version or later.
Is CVE-2026-22729 exploitable, and should I be worried? Whether CVE-2026-22729 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-22729 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-22729?
- Upgrade org.springframework.ai:spring-ai-vector-store to 1.1.3 or later
- Upgrade org.springframework.ai:spring-ai-vector-store to 1.0.4 or later

Other vulnerabilities in org.springframework.ai:spring-ai-vector-store

CVE-2026-40967 CVE-2026-22738