CVE Watchtower

CVE-2026-59369Spring AI Improper Neutralization of Special Elements in Data Query Logic

Spring

Vulnerability Summary

Typesense Vector Store filter expression injection bypasses tenant isolation. TypesenseVectorStore is vulnerable to a filter expression injection that can bypass application-enforced metadata filters. TypesenseFilterExpressionConverter escapes user-controlled filter values only as JSON string literals before embedding them in the filter_by string sent to Typesense. Typesense's own filter-query tokenizer does not treat those escapes as delimiting a literal value and instead splits on characters that can appear inside an unescaped value, so a crafted value can terminate the intended clause and introduce additional filter conditions of the attacker's choosing. Applications that incorporate untrusted input into a metadata filter value passed to SearchRequest.filterExpression(...) (or otherwise reach TypesenseVectorStore's filter conversion, including delete operations) are affected. An attacker who controls such a value can inject an additional clause that overrides or extends an application's own restrictions, such as a tenant- or permission-scoping filter, resulting in disclosure of documents that should not have been visible to them.
Severity Level
HIGH(7.5)
Published Date
Nov 19, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Reserved
This CVE ID is referenced in a public advisory, but the CVE Program has not published its official CVE Record yet. Full CVSS/CPE data from NVD will appear here once it does.
Root Weakness (CWE)
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.
CVSS v3.1 Base Metrics — Score 7.5 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityNone
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • Spring AI 2.0.0 through 2.0.2
  • Spring AI 1.1.0 through 1.1.9
  • Spring AI 1.0.0 through 1.0.10
Patched Versions
  • Spring AI 2.0.3 (open source)
  • Spring AI 2.0.2.1 (commercial support only)
  • Spring AI 1.1.10 (commercial support only)
  • Spring AI 1.0.11 (commercial support only)

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run Spring AI and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Nov 19, 2026Published
  • Nov 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Spring AI CVEsYou are reading CVE-2026-59369. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More Spring AI CVEs

External References

Data last checked: Nov 20, 2026 05:01 UTC