CVE-2026-47216
Received Received - Intake
Unauthenticated DoS in Typesense Search Engine

Publication date: 2026-06-12

Last updated on: 2026-06-12

Assigner: GitHub, Inc.

Description
Typesense is a fast, typo-tolerant search engine. Prior to versions 29.1 and 30.2, there is an unauthenticated denial-of-service vulnerability in the /multi_search endpoint. A specially crafted request can trigger an unhandled exception during request processing, causing the server process to terminate. This issue can be exploited over the network without authentication and results in service unavailability. The duration of impact may vary depending on system configuration and dataset size. This issue has been patched in versions 29.1 and 30.2.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-12
Last Modified
2026-06-12
Generated
2026-06-13
AI Q&A
2026-06-12
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
typesense typesense to 30.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-754 The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-47216 is a high-severity unauthenticated denial-of-service vulnerability in the Typesense search engine, specifically in the /multi_search endpoint.

A specially crafted request sent to this endpoint can trigger an unhandled exception during request processing, which causes the server process to terminate unexpectedly.

This results in the service becoming unavailable until it is restarted or recovered.

The vulnerability can be exploited remotely over the network without any authentication.

It affects Typesense versions prior to 29.1 and 30.2, with patches available in those versions.

Impact Analysis

This vulnerability can cause the Typesense server to crash and become unavailable, leading to denial of service.

Since the server process terminates unexpectedly, users relying on the search service will experience interruptions and loss of availability.

The duration of the impact depends on system configuration and dataset size, potentially causing prolonged downtime.

However, this vulnerability does not affect data confidentiality or integrity.

Mitigation Strategies

To mitigate this vulnerability, users are strongly advised to upgrade their Typesense server to the nearest patched version.

  • Upgrade to Typesense version 29.1 or later if you are on the 29.x branch.
  • Upgrade to Typesense version 30.2 or later if you are on the 30.x branch.

These updates patch the unauthenticated denial-of-service vulnerability in the /multi_search endpoint that can cause the server process to terminate.

Compliance Impact

This vulnerability causes an unauthenticated denial-of-service condition resulting in service unavailability. However, it does not impact data confidentiality or integrity.

While service availability is a component of many compliance standards such as GDPR and HIPAA, the provided information does not specify direct effects on compliance with these regulations.

Organizations relying on Typesense should consider the risk of service disruption in their compliance risk assessments and ensure timely patching to maintain availability requirements.

Detection Guidance

This vulnerability can be detected by monitoring for crashes or unexpected terminations of the Typesense server process, especially when handling requests to the /multi_search endpoint.

To detect potential exploitation attempts, you can capture and analyze network traffic targeting the /multi_search endpoint for unusual or malformed requests.

A simple command to test if your Typesense server is vulnerable is to send a specially crafted request to the /multi_search endpoint and observe if the server process terminates unexpectedly.

  • Using curl to send a test request: curl -X POST http://<typesense-server>:<port>/multi_search -d '<crafted_payload>'

Replace <typesense-server>, <port>, and <crafted_payload> with your server address, port, and a payload designed to trigger the vulnerability. Note that crafting such a payload requires knowledge of the vulnerability specifics, which are not detailed here.

Additionally, monitoring server logs for unhandled exceptions or crashes related to /multi_search requests can help detect exploitation attempts.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-47216. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart