Evidence · DiggingBeagle record
pgEdge RAG Server BM25 tenant isolation GHSA-w437-9mwm-j6vq
Primary or origin disclosure used to qualify the underlying mechanism, stated prerequisites and limits. CVE-2026-125325 GHSA-w437-9mwm-j6vq: shared mutable BM25 index is cleared/refilled/searched under separate locks; concurrent tenant-filtered queries may search index populated by different tenant. Fix creates per-request keyword index with concurrent test.
- Source role
- primary disclosure
Evidence record
Primary or origin disclosure used to qualify the underlying mechanism, stated prerequisites and limits. CVE-2026-125325 GHSA-w437-9mwm-j6vq: shared mutable BM25 index is cleared/refilled/searched under separate locks; concurrent tenant-filtered queries may search index populated by different tenant. Fix creates per-request keyword index with concurrent test.
Claim-level citations (3)
- supportspgEdge RAG concurrent keyword searches could include another tenant's documents: The pgEdge RAG Server advisory attributes mixed-tenant keyword search results to a shared mutable BM25 index whose clear, populate and search stages were guarded by separate locks; the correction uses a per-request index.
GHSA-w437-9mwm-j6vq, technical root cause, concurrent request test and fixed version
- supportspgEdge RAG concurrent keyword searches could include another tenant's documents: The security advisory documents the race but does not identify a particular customer document disclosed or retrospective logs proving actual cross-tenant responses.
GHSA-w437-9mwm-j6vq, concurrency explanation, tenant filters and 2.0.0 fix
- supportspgEdge RAG concurrent keyword searches could include another tenant's documents: pgEdge RAG Server reused a mutable BM25 keyword index across requests. Clearing, filling and searching that index under separate locks let concurrent tenant-filtered searches consult a different tenant's indexed documents.
GHSA-w437-9mwm-j6vq, concurrency explanation, tenant filters and 2.0.0 fix