{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-47225 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-47225 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-47225 is a medium-severity vulnerability in typesense, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47225 and fix it if it is affected.\n\nWhat it is: CVE-2026-47225 is a medium-severity vulnerability in typesense, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47225 in the wild and no public exploit code.\n\nAffected product: typesense. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-47225/ (Markdown: https://insights.sbomify.com/CVE-2026-47225/index.md)","id":"CVE-2026-47225","markdown":"https://insights.sbomify.com/CVE-2026-47225/index.md","name":"CVE-2026-47225","record":{"aliases":["GHSA-97x4-gm45-jpcw"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Typesense search engine","requires_auth":"low_privilege","summary":"Attackers can view restricted search results by exploiting cache isolation flaws when using scoped API keys and server-side caching.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-524","name":"Use of Cache Containing Sensitive Information"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Improper Search Cache Isolation for Scoped Search API Keys in Typesense","id":"CVE-2026-47225","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Admidio: Authorization bypass in file_delete enables cross-folder file removal by authenticated users without delete privileges","id":"CVE-2026-47226"},"packages":[],"prev":{"headline":"NanaZip: Heap buffer-overflow read in NanaZip LVM metadata CRC check","id":"CVE-2026-47224"},"products":["typesense"],"published":"2026-06-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-12","vendors":["typesense"]},"summary":"Attackers can view restricted search results by exploiting cache isolation flaws when using scoped API keys and server-side caching.","url":"https://insights.sbomify.com/CVE-2026-47225/"}