CVE-2026-125325

Concurrent pgEdge searches could return another tenant's documents

pgEdge · RAG Server keyword search

First documented disclosure · Review checkpoint

Summary

Parallel queries reused mutable keyword-index state across differently filtered document sets. Documents from another tenant could appear in results. The maintainer says server logs cannot retrospectively identify the affected responses.

Severity and exploitation evidence

Medium · 5.9/10 · CVSS 3.1. Severity source.

Exploitation not established: The reviewed advisory does not report malicious exploitation.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Parallel queries reused mutable keyword-index state across differently filtered document sets.

Conditions required

Overlapping queries used the same pipeline with different search filters.

Potential impact

Documents from another tenant could appear in results. The maintainer says server logs cannot retrospectively identify the affected responses.

Affected versions and configurations

Maintainer lists releases through 1.0.0. CNA describes versions before 2.0.0.

Fix and mitigation status

2.0.0.

Practical next steps

Upgrade RAG Server and test concurrent searches across tenant boundaries.

Operating lesson

Give AI retrieval and tool services database credentials scoped to the data they need.

Evidence and limits

The public disclosure was on 2026-09-03. The CVE record was published on 2026-11-10.

Sources