CVE-2026-125325
Received Received - Intake

Information Leak in pgEdge RAG Server

Publication date: 2026-11-10

Last updated on: 2026-11-10

Assigner: GitHub, Inc.

Description
pgEdge RAG Server is an API server for retrieval-augmented generation over PostgreSQL content using pgvector. Prior to 2.0.0, the BM25 keyword index is a single per-pipeline object shared by the unauthenticated query endpoint, and concurrent requests lock its clear, refill, and search operations separately. This allows one request to search a corpus populated through another request's search filter, which can return documents belonging to a different tenant or customer without malformed input. The affected responses cannot be identified retrospectively from the server logs. This issue is fixed in version 2.0.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-10
Last Modified
2026-11-10
Generated
2026-11-10
AI Q&A
2026-11-10
EPSS Evaluated
N/A
NVD
CVE-2026-125325
EUVD
EUVD-2026-121707

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
pgedge rag_server 2.0.0
pgedge pgedge_rag_server to 2.0.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-488 The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session.
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The vulnerability in pgEdge RAG Server versions 1.0.0 and earlier involves a shared BM25 keyword index used for search operations. This index is a single object per pipeline shared across all unauthenticated requests. Concurrent requests can lock and modify this index separately, causing one request's search to return documents from another tenant's corpus without any malformed input. The issue is fixed in version 2.0.0 by building the index per request instead of sharing it.

Detection Guidance

Detecting this vulnerability requires checking the pgEdge RAG Server version and monitoring for cross-tenant data leaks during concurrent requests. Verify if the server is running version 1.0.0 or earlier. Monitor logs for responses containing unexpected tenant data under concurrent load. No specific commands are provided in the resources, but you can check the server version via API or logs and simulate concurrent requests to observe data leakage.

Impact Analysis

This vulnerability allows unauthorized access to documents belonging to different tenants or customers during concurrent search requests. Since the query endpoint is unauthenticated, any remote caller can potentially receive sensitive data from another tenant. The affected responses cannot be identified from server logs, so any responses served under concurrent load on affected versions should be treated as potentially including another tenant's documents.

Compliance Impact

This vulnerability could lead to unauthorized data exposure, violating data isolation requirements in GDPR and HIPAA. GDPR requires strict access controls and data segregation, while HIPAA mandates safeguards to protect patient data. The cross-tenant data leakage undermines these compliance requirements by allowing unauthorized access to sensitive information.

Mitigation Strategies
  • Upgrade pgEdge RAG Server to version 2.0.0 or later to eliminate the shared index vulnerability.
  • Temporarily disable the keyword index by setting hybrid_enabled: false in the configuration or passing disable_hybrid per request as a workaround.
  • Assume any responses served under concurrent load on affected versions may include another tenant's documents and treat them as potentially compromised.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-125325. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...