CVE-2026-132750 json
Meilisearch before 1.55.1 and 1.56.x before 1.56.1 Denial of Service via filter-parser Quadratic Memory Consumption
published 1h ago modified 35m ago also EUVD-2026-129366
- cvss
- 7.1
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- meilisearch meilisearch 1.55.1, 1.56.1
Is CVE-2026-132750 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- meilisearch meilisearch
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/meilisearch/meilisearch/pull/6695
issue-tracking, patch
-
github.com
/meilisearch/meilisearch/commit/5ec13cf578494a771e2239a8cee1ca6be0e042a5
patch
-
github.com
/meilisearch/meilisearch/releases/tag/v1.55.1
release-notes
-
github.com
/meilisearch/meilisearch/releases/tag/v1.56.1
release-notes
-
github.com
/meilisearch/meilisearch/blob/v1.53.1/crates/filter-parser/src/lib.rs#L176-L182
technical-description
-
vulncheck.com
/advisories/meilisearch-before-1.55.1-and-1.56-x-before-1.56.1-denial-of-service-via-filter-parser-quadratic-m
third-party-advisory
Sources
- CVE List CVE-2026-132750
- NVD CVE-2026-132750
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.