cve.bz

CVE-2026-125325 pgEdge RAG Server shared keyword index leaked results between concurrent unauthenticated requests

5.9 mediumEPSS 0.3%Fix available

Medium (5.9) in pgedge pgedge-rag-server. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/pgEdge/pgedge-rag-server 1.0.1-0.20260729020411-a09d4872356b.

On this page
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.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
CWE-488 Exposure of Data Element to Wrong Session
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-125325 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125325?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125325?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125325 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-125325

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-125325](https://cve.bz/cve/badge/CVE-2026-125325.svg)](https://cve.bz/cve/CVE-2026-125325)

HTML:

<a href="https://cve.bz/cve/CVE-2026-125325"><img src="https://cve.bz/cve/badge/CVE-2026-125325.svg" alt="CVE-2026-125325"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
pgedge-rag-server< 2.0.0

Fix and patched versions

  • github.com/pgEdge/pgedge-rag-server (Go): fixed in 1.0.1-0.20260729020411-a09d4872356b

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-w437-9mwm-j6vqGogithub.com/pgEdge/pgedge-rag-server<1.0.1-0.20260729020411-a09d4872356b1.0.1-0.20260729020411-a09d4872356b

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON