# CVE-2026-22729: CVE-2026-22729: JSONPath Injection in Spring AI Vector Stores FilterExpressionConverter > Authenticated attackers can inject JSONPath logic to bypass metadata access controls and read unauthorized documents in Spring AI vector stores. - **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Mar 2026 - **Updated:** 18 Mar 2026 - **Also known as:** GHSA-rp9g-qx29-88cp ## What is CVE-2026-22729? CVE-2026-22729 is a high-severity code injection vulnerability in VMware Spring AI, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-917 (Improper Neutralization of Special Elements used in an Expression Language Statement) ## Which versions are affected by CVE-2026-22729? 4 open source packages ship an affected version, including org.springframework.ai:spring-ai-vector-store. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.ai:spring-ai-vector-store` | Maven | All versions | 1.0.4 | | `org.springframework.ai:spring-ai-vector-store` | Maven | All versions | 1.0.4 | | `org.springframework.ai:spring-ai-vector-store` | Maven | From 1.1.0-M1 | 1.1.3 | | `org.springframework.ai:spring-ai-vector-store` | Maven | From 1.1.0-M1 | 1.1.3 | Products: Vmware Spring Ai. ## How do I fix CVE-2026-22729? Upgrade org.springframework.ai:spring-ai-vector-store to a fixed version for your release line: 1.0.4 or 1.1.3. ## Is CVE-2026-22729 being exploited? There is no known exploitation of CVE-2026-22729 in the wild and no public exploit code. ## Other vulnerabilities in VMware Spring AI - [CVE-2026-22738](https://insights.sbomify.com/CVE-2026-22738/): SpEL Injection via Unescaped Filter Key in SimpleVectorStore Leads to Remote Code Execution (critical 9.8) - [CVE-2026-40978](https://insights.sbomify.com/CVE-2026-40978/): Spring AI has SQL Injection in CosmosDBVectorStore.doDelete() (high 8.8) - [CVE-2026-22730](https://insights.sbomify.com/CVE-2026-22730/): CVE-2026-22730: SQL Injection in Spring AI MariaDBFilterExpressionConverter (high 8.8) - [CVE-2026-47835](https://insights.sbomify.com/CVE-2026-47835/): Spring AI vector store metadata filtering to handle special characters in Elasticsearch, OpenSearch, and GemFire Vector Stores (high 8.6) - [CVE-2026-41705](https://insights.sbomify.com/CVE-2026-41705/): Spring AI's MilvusVectorStore#doDelete(List) implementation is vulnerable to filter-expression injection via unsanitized document IDs (high 8.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-22729 and fix it if it is affected. What it is: CVE-2026-22729 is a high-severity code injection vulnerability in VMware Spring AI, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-22729 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.ai:spring-ai-vector-store (Maven): affected all versions; fixed in 1.0.4 - org.springframework.ai:spring-ai-vector-store (Maven): affected all versions; fixed in 1.0.4 - org.springframework.ai:spring-ai-vector-store (Maven): affected from 1.1.0-M1; fixed in 1.1.3 - org.springframework.ai:spring-ai-vector-store (Maven): affected from 1.1.0-M1; fixed in 1.1.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-22729/ (Markdown: https://insights.sbomify.com/CVE-2026-22729/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22729 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22729 - OSV: https://osv.dev/vulnerability/CVE-2026-22729 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-22729/ Summaries are generated and may contain mistakes; the official description above is the record.