This vulnerability allows a user exploiting improperly isolated search caches to retrieve data from other authorization contexts. The flaw occurs when Typesense uses both server‑side cached results and Scoped Search API Keys that contain embedded filters. Under a specific sequence of requests, the cache contains results from one key and serves them to a request that should be limited by a different key, causing exposure of restricted search results. The consequence is that an attacker could see data that should have been restricted by its Scoped Search API Key, leading to privacy or confidentiality violations.

The affected product is Typesense, a typo‑tolerant search engine. Versions prior to 29.1 for the 29.x line and prior to 30.2 for the 30.x line are vulnerable. Any deployment that enables both server‑side result caching and uses Scoped Search API Keys with embedded filters for collection‑level restrictions is at risk.

The CVSS score of 6.0 categorizes this flaw as moderate severity, and the EPSS score of less than 1% indicates a very low probability of exploitation in the wild. The vulnerability is not in the CISA KEV catalog. Exploitation requires the attacker to control request sequencing against the same cached index and use valid scoped keys, which suggests a need for network access to the Typesense instance and a certain level of interaction. Because the attack surface is limited to environments exposing the API and cache features, the risk remains moderate but could lead to sensitive data leakage if the scenario is met.