Spring AiFramework / library · VMware
CVE-2026-22729
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 · uneditedA 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.
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 confidenceA JSONPath injection vulnerability in Spring AI's AbstractFilterExpressionConverter allows authenticated users to bypass metadata-based access controls. User-controlled input passed to FilterExpressionBuilder is concatenated into JSONPath queries without proper escaping of special characters like quotes, ||, and &&, enabling injection of arbitrary JSONPath logic to access unauthorized documents.
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
>= 1.0.0, < 1.0.4>= 1.1.0, < 1.1.3CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Spring AI versionLocate the Spring AI dependency in your project (Maven pom.xml, Gradle build.gradle, or the spring-ai-core JAR manifest) and note the exact version numberAffected if The version is 1.0.0 through 1.0.3, or 1.1.0 through 1.1.2
-
Determine if FilterExpressionBuilder is in useSearch your codebase for imports or references to org.springframework.ai.filter.expression.FilterExpressionBuilder or classes extending AbstractFilterExpressionConverterAffected if Your application uses FilterExpressionBuilder to construct filter expressions from user data
-
Audit filter input sourcesTrace data flow to FilterExpressionBuilder methods and identify which request parameters, headers, or body fields feed into filter constructionAffected if User-supplied or external input is passed directly to filter expression methods without sanitization
-
Check for unescaped special characters in filter logicReview how filter values are processed; look for code that concatenates raw user input into JSONPath query strings without applying escaping for quotes, ||, or &&Affected if The application builds JSONPath queries by concatenating unsanitized user input containing special characters
-
Verify access control enforcementTest whether filter-based access controls properly restrict document access when injecting JSONPath operators (e.g., ||, &&) or alternate field values in filter parametersAffected if Injected JSONPath logic can bypass intended metadata-based access restrictions
You are affected if your Spring AI version falls within 1.0.0-1.0.3 or 1.1.0-1.1.2 AND user input flows into FilterExpressionBuilder without escaping special characters that could alter JSONPath query semantics.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.41.1.3
Implement proper escaping of user-supplied values in filter expressions before they are concatenated into JSONPath queries, ensuring special characters cannot alter query semantics.
Spring AI 1.0.4 or 1.1.3
- Identify your current Spring AI version by checking your project's pom.xml or build.gradle file
- For Maven projects: Update the spring-ai-bom version in your dependencyManagement section to 1.0.4 or 1.1.3, for example: <version.spring.ai>1.0.4</version.spring.ai>
- For Maven projects: Update all spring-ai-* starter dependencies to the same version (1.0.4 or 1.1.3)
- For Gradle projects: Update the springAiVersion property in gradle.properties to 1.0.4 or 1.1.3, for example: springAiVersion=1.0.4
- Run mvn clean compile or ./gradlew build to fetch the updated dependencies
- Review the Spring AI 1.0.4 and 1.1.3 release notes for any relevant changes to filter expression handling
- Test your application's filter expressions and document access controls to verify the fix works correctly
- Ensure multi-tenant isolation and role-based access controls still function as expected 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
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22729 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22729 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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