Skip to content

← Actionable
High, CVSS 7.5amended

pgEdge RAG Server unbounded corpus read allows resource exhaustion from unauthenticated requests

CVE-2026-125327GHSA-5qg5-rgp6-j5m5

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
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-125327: 0.45% estimated exploitation activity in the next 30 days; percentile 39.35 (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 An unauthenticated caller able to reach the query endpoint could exhaust database and server resources with ordinary, inexpensive requests. The keyword-search arm read the entire corpus on every request and rebuilt an in-memory BM25 index from it, so the cost of serving a query scaled with the size of the source table rather than with the size of the result set. Each request cost the server and the tenant's database far more than it cost the caller to make, which makes this a materially more effective denial-of-service lever than flooding the endpoint with ordinary requests. The amplification factor grows with corpus size, so the largest deployments are the most exposed. Hybrid search was enabled by default and configured per pipeline rather than per request, so a caller could not opt out of the keyword arm and an operator could not leave it available to some requests but not others. Who is affected: any deployment of pgEdge RAG Server at `1.0.0` or earlier, including…

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

    Amended from osv record GHSA-5qg5-rgp6-j5m5

  2. Revision 1 · created ·

    Published from ghsa record GHSA-5qg5-rgp6-j5m5

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-125327

Advisory: pgEdge RAG Server unbounded corpus read allows resource exhaustion from unauthenticated requests
IDs: CVE-2026-125327, GHSA-5qg5-rgp6-j5m5
Record: https://patchnext.com/advisories/cve-2026-125327 (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: High (CVSS 7.5)
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-5qg5-rgp6-j5m5 (GitHub-reviewed advisory GHSA-5qg5-rgp6-j5m5 lists affected ranges: Go github.com/pgEdge/pgedge-rag-server >=0 <1.0.1-0.20260729020411-a09d4872356b)
- Verified: https://osv.dev/vulnerability/GHSA-5qg5-rgp6-j5m5 (OSV record GHSA-5qg5-rgp6-j5m5 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…