Elasticsearch 9.5.1: false-positive matches in certain boolean queries

What to do

• Check whether your product depends on Elastic Cloud. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 6d 7h it lasted.

  Anything that failed between 2026-08-14 09:22 UTC and 2026-08-20 17:09 UTC may need a replay.

• Subscribe to Elastic Cloud's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=elastic-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Elastic Cloud 2

1. identifiedAug 14, 2026, 9:22 AM UTC

   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.

   provider

2. resolvedAug 20, 2026, 5:09 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.