Search

Companies / Elastic Cloud / incidents

Elastic Cloud: Elasticsearch 9.5.1: false-positive matches in certain boolean queries

Impact: majorStatus: resolvedStarted Resolved (6 d)2 updatesSource: stspg.io (opens in new tab)
Summary

Elastic Cloud reported a major Elasticsearch 9.5.1 issue causing false-positive matches in boolean queries combining multi-value terms in must, filter, or should clauses with must_not on fields with disabled indexing. It ran from 2026-08-14 09:22 UTC to 2026-08-20 17:09 UTC (6 days 7 h); Elasticsearch 9.5.2 fixes it, and customers on 9.5.0 or 9.5.1 should upgrade.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Timeline of updates

  1. identified

    Elasticsearch 9.5.1 contains a known issue where boolean queries containing a must, filter, or should clause using a multi-value terms query, alongside a must_not clause on fields with disabled indexing, can still return false-positive matches. While the patch in 9.5.1 (https://github.com/elastic/elasticsearch/pull/155936) resolved the bulk-scorer defect for term and range query paths; multi-value terms queries utilize a different Lucene query type that was not covered by that fix. Time Series Data Streams (TSDB) and columnar indices/data streams remain affected for this query pattern, as indexing is disabled by default on those fields. Affected terms queries may return false-positive matches (including documents that should have been excluded) and report higher document counts than expected. No error is raised, so queries will appear to complete successfully. What you can do: - If you have not yet upgraded to 9.5.*, we recommend deferring the upgrade until version 9.5.2 is available. - If you are already running 9.5.*, contact Elastic Support if you need help determining whether your searches are affected. We have identified the root cause, a fix is in progress, and we are preparing a patch release. We will provide a further update when the fix is ready.

  2. resolved

    Elasticsearch 9.5.2 has been released and contains the fix for this issue. Customers running 9.5.0 or 9.5.1 should upgrade to 9.5.2. At this time we are considering this issue resolved and will be providing no further updates.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Elastic Cloud profile · Recent Elastic Cloud incidents · Markdown · JSON