CVE-2026-47225

MEDIUMPre-NVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.0
EG Score
6.0(medium)
EPSS
13.2%
KEV
Not listed

Published

June 12, 2026

Last Modified

June 15, 2026

Advisory Details (1)

Auto-updated Jun 13, 2026
Patch available. Sources: github.
github Patch Available

Improper Search Cache Isolation for Scoped Search API Keys in Typesense · Advisory · typesense/typesense · GitHub

https://github.com/typesense/typesense/security/advisories/GHSA-97x4-gm45-jpcw

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 67× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 03:24 UTCEG score recompute
  3. 2026-07-10 03:25 UTCEG score recompute
  4. 2026-07-09 19:10 UTCEPSS rescore
  5. 2026-07-09 00:57 UTCEG score recompute
  6. 2026-07-08 15:16 UTCEPSS rescore
  7. 2026-07-08 00:52 UTCEG score recompute
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-07 01:05 UTCEG score recompute
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 18:58 UTCEG score recompute
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-04 19:11 UTCEG score recompute
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-03 18:45 UTCEG score recompute
  17. 2026-07-02 18:59 UTCEG score recompute
  18. 2026-07-01 19:13 UTCEG score recompute
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 19:20 UTCEG score recompute
  22. 2026-06-29 19:34 UTCEG score recompute
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-28 19:48 UTCEG score recompute
Show 42 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-27 20:02 UTCEG score recompute
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-26 20:14 UTCEG score recompute
  7. 2026-06-25 20:28 UTCEG score recompute
  8. 2026-06-25 13:49 UTCEPSS rescore
  9. 2026-06-24 20:41 UTCEG score recompute
  10. 2026-06-24 14:05 UTCEPSS rescore
  11. 2026-06-23 21:33 UTCEPSS rescore
  12. 2026-06-23 21:33 UTCEPSS rescore
  13. 2026-06-23 20:19 UTCEG score recompute
  14. 2026-06-22 20:12 UTCEG score recompute
  15. 2026-06-22 14:25 UTCEPSS rescore
  16. 2026-06-22 14:25 UTCEPSS rescore
  17. 2026-06-21 20:11 UTCEG score recompute
  18. 2026-06-21 14:56 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 01:59 UTCEPSS rescore
  21. 2026-06-21 01:59 UTCEPSS rescore
  22. 2026-06-20 20:23 UTCEG score recompute
  23. 2026-06-19 19:26 UTCEPSS rescore
  24. 2026-06-19 19:26 UTCEPSS rescore
  25. 2026-06-19 19:06 UTCEG score recompute
  26. 2026-06-18 19:17 UTCEG score recompute
  27. 2026-06-18 17:52 UTCEPSS rescore
  28. 2026-06-18 17:52 UTCEPSS rescore
  29. 2026-06-17 19:10 UTCEG score recompute
  30. 2026-06-17 17:53 UTCEPSS rescore
  31. 2026-06-16 19:24 UTCEG score recompute
  32. 2026-06-16 17:53 UTCEPSS rescore
  33. 2026-06-15 19:37 UTCEG score recompute
  34. 2026-06-15 17:49 UTCEPSS rescore
  35. 2026-06-15 17:49 UTCEPSS rescore
  36. 2026-06-14 23:18 UTCEPSS rescore
  37. 2026-06-14 19:47 UTCEG score recompute
  38. 2026-06-13 23:00 UTCEPSS rescore
  39. 2026-06-13 20:01 UTCEG score recompute
  40. 2026-06-12 23:12 UTCEPSS rescore
  41. 2026-06-12 20:13 UTCEG score recompute
  42. 2026-06-12 20:13 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-47225?
CVE-2026-47225 is a medium vulnerability published on June 12, 2026. 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…
When was CVE-2026-47225 disclosed?
CVE-2026-47225 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47225 actively exploited?
CVE-2026-47225 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47225?
CVE-2026-47225 has a CVSS v3 base score of 6.0 (NVD).
How do I remediate CVE-2026-47225?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47225, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-47225

Explore →

Is Your Infrastructure Affected by CVE-2026-47225?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs