Skip to content

← Actionable
Medium, CVSS 5.9amended

pgEdge RAG Server shared keyword index leaked results between concurrent unauthenticated requests

CVE-2026-125325GHSA-w437-9mwm-j6vq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/pgEdge/pgedge-rag-server 1.0.1-0.20260729020411-a09d4872356b), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-125325: 0.27% estimated exploitation activity in the next 30 days; percentile 19.60 (FIRST EPSS, 2026-11-14). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact Documents belonging to one caller could be returned to another. Where an application passes a customer or tenant identifier as a search filter, that scoping could be defeated by ordinary concurrent traffic. No injection and no malformed input are required — normal load is enough. The BM25 keyword index was a single per-pipeline object shared by every request. A request cleared it, refilled it from its own filtered corpus and then searched it, taking a separate lock for each step rather than holding the sequence as a unit. Concurrent requests therefore interleaved, and a search could run against a corpus that a different request's filter had populated. Who is affected: any deployment of pgEdge RAG Server at `1.0.0` or earlier, including all alpha and beta pre-releases, that serves concurrent queries — most acutely those relying on a search filter to separate tenants or customers. The query endpoint is unauthenticated in the affected versions…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-w437-9mwm-j6vq

  2. Revision 1 · created ·

    Published from ghsa record GHSA-w437-9mwm-j6vq

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-125325

Advisory: pgEdge RAG Server shared keyword index leaked results between concurrent unauthenticated requests
IDs: CVE-2026-125325, GHSA-w437-9mwm-j6vq
Record: https://patchnext.com/advisories/cve-2026-125325 (revision 2, source checked 13 Nov 2026, 06:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/pgEdge/pgedge-rag-server 1.0.1-0.20260729020411-a09d4872356b. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/pgEdge/pgedge-rag-server: affected < 1.0.1-0.20260729020411-a09d4872356b; fixed in 1.0.1-0.20260729020411-a09d4872356b

## Suggested inspection (read-only)
- Go github.com/pgEdge/pgedge-rag-server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/pgEdge/pgedge-rag-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w437-9mwm-j6vq (GitHub-reviewed advisory GHSA-w437-9mwm-j6vq lists affected ranges: Go github.com/pgEdge/pgedge-rag-server >=0 <1.0.1-0.20260729020411-a09d4872356b)
- Verified: https://osv.dev/vulnerability/GHSA-w437-9mwm-j6vq (OSV record GHSA-w437-9mwm-j6vq lists affected ranges: Go github.com/pgEdge/pgedge-rag-server >=0 <1.0.1-0.20260729020411-a09d4872356b (fixed))

Commands are suggestions: review each one before running it.

Loading voting…