CVE-2026-47225
MediumCVSS 6.0Exploitation Probability (EPSS)
Low risk13th percentile — higher than 13% of all known CVEs
Summary
Typesense, a typo-tolerant search engine, has a cache isolation issue affecting search requests that use server-side search result caching and Scoped Search API Keys. Under specific request ordering, cached search results could be reused across requests with different Scoped Search API Key constraints, leading to unintended disclosure of search results.
Risk Assessment
Organizations may experience unauthorized access to search results, potentially exposing sensitive data across authorization contexts. This could lead to serious privacy and data security breaches.
Recommendation
It is recommended to upgrade to versions 29.1 or 30.2 to mitigate this vulnerability. Additionally, reviewing and adjusting the configuration of API keys and caching may help minimize future risks.
Original NVD description (English source)
Typesense is a fast, typo-tolerant search engine. Prior to versions 29.1 and 30.2, there is a cache isolation issue affecting search requests that use both server-side search result caching and Scoped Search API Keys. Under specific request ordering, cached search results could be reused across requests with different Scoped Search API Key constraints. This could result in a request receiving search results that should have been restricted by its Scoped Search API Key. This issue only affects search requests that use both server-side search result caching and Scoped Search API Keys with embedded filters to restrict access to search results within a collection. This vulnerability may result in unintended disclosure of search results across scoped authorization contexts. This issue has been patched in versions 29.1 and 30.2.