Skip to main content
Menu
CVEs

CVE

Meilisearch denial of service in filter parser

CVE-2026-132750EUVD-2026-129366Published Updated Summary written by a model

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.55.1, 1.56.1
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Meilisearch versions before 1.55.1, and 1.56.x before 1.56.1 A very long filter (roughly 100 KB, e.g. a _geoPolygon with thousands of coordinates) is sent to the search endpoint

Summary

Meilisearch, a search engine, has a flaw in its filter parser that lets an attacker holding a search API key exhaust server memory. The attacker can reach it remotely by sending a filter of about 100 KB to the search endpoint, which can crash the server and take all indexes offline.

Original description

Meilisearch before 1.55.1 and 1.56.x before 1.56.1 contains a quadratic memory consumption vulnerability in filter-parser that allows attackers with a search API key to exhaust server memory. Attackers can send a roughly 100 KB filter, such as a _geoPolygon with thousands of coordinates, to the search endpoint, crashing the server and taking all indexes offline.

Who should check

Teams running Meilisearch before 1.55.1, or 1.56.x before 1.56.1, that expose the search API to clients holding a search API key

“Meilisearch before 1.55.1 and 1.56.x before 1.56.1”

vulncheck.com

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Meilisearch versions before 1.55.1, and 1.56.x before 1.56.1 A very long filter (roughly 100 KB, e.g. a _geoPolygon with thousands of coordinates) is sent to the search endpoint
  • Upgrade to a fixed version: 1.55.1, 1.56.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-132750 (Meilisearch before 1.55.1 and 1.56.x before 1.56.1 Denial of Service via filter-parser Quadratic Memory Consumption), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-132750 (entry last updated 2026-11-18):
Affected:
- meilisearch meilisearch: fixed in 1.55.1; from 1.56.0, fixed in 1.56.1
Fixed versions: 1.55.1, 1.56.1.
Conditions (all must be true for the bug to be hit):
- Meilisearch versions before 1.55.1, and 1.56.x before 1.56.1 (source: https://www.vulncheck.com/advisories/meilisearch-before-1.55.1-and-1.56-x-before-1.56.1-denial-of-service-via-filter-parser-quadratic-memory-consumption)
- A very long filter (roughly 100 KB, e.g. a _geoPolygon with thousands of coordinates) is sent to the search endpoint (source: https://www.vulncheck.com/advisories/meilisearch-before-1.55.1-and-1.56-x-before-1.56.1-denial-of-service-via-filter-parser-quadratic-memory-consumption)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-132750 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132750 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/meilisearch/meilisearch/pull/6695
- https://github.com/meilisearch/meilisearch/commit/5ec13cf578494a771e2239a8cee1ca6be0e042a5
- https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1
- https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1
- https://github.com/meilisearch/meilisearch/blob/v1.53.1/crates/filter-parser/src/lib.rs#L176-L182
- https://www.vulncheck.com/advisories/meilisearch-before-1.55.1-and-1.56-x-before-1.56.1-denial-of-service-via-filter-parser-quadratic-memory-consumption
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-132750
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132750"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • meilisearch meilisearch

    fixed in 1.55.1; From 1.56.0 · fixed in 1.56.1

Evidence 8

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-132750

Is CVE-2026-132750 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A crafted, very long filter sent to the search endpoint makes Meilisearch's filter parser use memory that grows quadratically with the filter's size. Roughly 100 KB of input, such as a _geoPolygon with thousands of coordinates, can exhaust server memory, crashing the server and taking all indexes offline.Source: vulncheck.com

Which versions are affected by CVE-2026-132750?

meilisearch: before 1.55.1; from 1.56.0 before 1.56.1.Source: cve.now feed data

Am I affected, and how do I check?

Meilisearch versions before 1.55.1, and 1.56.x before 1.56.1, are affected. Check the running version with the Meilisearch version endpoint or the server startup output.Source: vulncheck.com

How do I fix CVE-2026-132750?

Upgrade to Meilisearch 1.55.1 or later on the 1.55 line, or to 1.56.1 or later on the 1.56 line.Source: vulncheck.com

More CVEs