CVE-2026-22729 — spring-ai-vector-store
HIGHCVE-2026-22729 is a high-severity (CVSS 8.6) Expression Language Injection vulnerability in org.springframework.ai:spring-ai-vector-store. A fix is available for org.springframework.ai:spring-ai-vector-store — see the affected versions and patch details below.
CVE-2026-22729: JSONPath Injection in Spring AI Vector Stores FilterExpressionConverter
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22729.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.ai:spring-ai-vector-store☕org.springframework.ai:spring-ai-vector-storeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.ai:spring-ai-vector-store | ≥ 1.1.0-M1&&< 1.1.3 | 1.1.3org.springframework.ai:spring-ai-vector-store:1.1.3 |
| ☕Maven | org.springframework.ai:spring-ai-vector-store | all versions | 1.0.4org.springframework.ai:spring-ai-vector-store:1.0.4 |
Affected Products
spring aivmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.ai:spring-ai-vector-store, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.ai:spring-ai-vector-store to 1.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22729 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2026-22729 in your dependencies?
Find it across Maven, including transitive dependencies.