Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 12 Jun 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Typesense
Typesense typesense |
|
| Vendors & Products |
Typesense
Typesense typesense |
Fri, 12 Jun 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 12 Jun 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Improper Search Cache Isolation for Scoped Search API Keys in Typesense | |
| Weaknesses | CWE-524 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-06-12T18:30:36.952Z
Reserved: 2026-05-18T22:25:21.259Z
Link: CVE-2026-47225
Updated: 2026-06-12T18:30:32.987Z
Status : Deferred
Published: 2026-06-12T18:16:34.783
Modified: 2026-06-15T21:05:18.653
Link: CVE-2026-47225
No data.
OpenCVE Enrichment
Updated: 2026-06-12T20:19:31Z