CVE-2026-125327: github.com/pgEdge/pgedge-rag-server · pgEdge RAG Server unbounded corpus read allows resource exhaustion from unauthenticated requests
Affects github.com/pgEdge/pgedge-rag-serverSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 1.0.1-0.20260729020411-a09d4872356b soon.
Data as of 12 Nov 2026, 21:22 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 1.0.1-0.20260729020411-a09d4872356b
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade github.com/pgEdge/pgedge-rag-server to 1.0.1-0.20260729020411-a09d4872356b.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/pgEdge/pgedge-rag-server | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to pgEdge RAG Server version 2.0.0 or later, which introduces a configurable limit on corpus reads and allows disabling the hybrid search arm per query. Until upgrading, mitigate by placing the server behind an authenticating and rate-limiting reverse proxy. Alternatively, disable hybrid search per pipeline by setting 'hybrid_enabled: false', which removes the unbounded read but reduces keyword recall. Neither workaround fully replaces upgrading.
Description
pgEdge RAG Server versions 1.0.0 and earlier have an unbounded corpus read vulnerability at the query endpoint, allowing unauthenticated callers to exhaust database and server resources. The server rebuilds an in-memory BM25 index from the entire corpus on every request without limiting the read size, causing resource consumption to scale with corpus size. Hybrid search is enabled by default and cannot be disabled per request, increasing exposure. This can lead to a denial-of-service condition. The issue is fixed in version 2.0.0 by introducing a configurable limit on documents read and allowing disabling the expensive keyword search per query.
References
- github.com/pgEdge/pgedge-rag-server/security/advisories/GHSA-5qg5-rgp6-j5m5 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-125327 (opens in a new tab)
- github.com/pgEdge/pgedge-rag-server/pull/44 (opens in a new tab)
- github.com/pgEdge/pgedge-rag-server/commit/a09d4872356b510c81f11591845445c33ff45a84 (opens in a new tab)
- github.com/pgEdge/pgedge-rag-server (opens in a new tab)
- github.com/pgEdge/pgedge-rag-server/releases/tag/v2.0.0 (opens in a new tab)