User-controlled filter keys can bypass Coherence metadata filtering

HIGH | NOVEMBER 19, 2026 | CVE-2026-59344

Description

CoherenceVectorStore is vulnerable to a metadata filter bypass when evaluating filter expressions against an Oracle Coherence backend.

CoherenceFilterExpressionConverter builds its underlying Coherence extractor directly from a quoted key in the Spring AI filter DSL, without validating that the key text represents a literal metadata field name. Certain key strings are interpreted by Coherence as operations on the metadata object itself rather than as a lookup of that field, which can cause a filter to match documents it was never meant to match.

Applications that pass externally influenced or model-generated filter expressions to SearchRequest.filterExpression(...) against a Coherence-backed vector store are affected. An attacker able to control such an expression may cause metadata-based restrictions (for example tenant or document-scoping filters) to be bypassed, resulting in disclosure of documents that should have been excluded from the results.

Affected Spring Products and Versions

Spring AI:

  • 2.0.0 - 2.0.2
  • 1.1.0 - 1.1.9
  • 1.0.0 - 1.0.10

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.
Fix versionAvailability
2.0.3OSS
2.0.2.1Enterprise Support Only
1.1.10Enterprise Support Only
1.0.11Enterprise Support Only

No further mitigation steps are necessary.

Credit

The issue was reported responsibly by Tran Hoang Phuc Quan - https://github.com/PhucQuan ([email protected]) from Viettel Networks

History

  • 2026-11-19: Initial vulnerability report published.

Get ahead

VMware offers training and certification to turbo-charge your progress.

Learn more

Get support

TrueSource Spring Enterprise offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.

Learn more

Upcoming events

Check out all the upcoming events in the Spring community.

View all