# CVE-2026-125327: pgEdge RAG Server unbounded corpus read allows resource exhaustion from unauthenticated requests


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-5qg5-rgp6-j5m5

## What is CVE-2026-125327?

CVE-2026-125327 is a high-severity vulnerability in pgedge-rag-server, published on 10 Nov 2026. 

### Official description

pgEdge RAG Server is an API server for retrieval-augmented generation over PostgreSQL content using pgvector. Prior to 2.0.0, the unauthenticated query endpoint uses FetchDocuments in internal/database/search.go to read the entire filtered corpus without a LIMIT and rebuild an in-memory BM25 index on every request. Because HybridEnabled is set by default in internal/config/loader.go and the endpoint has no rate limit, inexpensive remote queries can impose database and CPU work proportional to corpus size and exhaust service resources. This issue is fixed in version 2.0.0.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-405 (Asymmetric Resource Consumption (Amplification))

## Which versions are affected by CVE-2026-125327?

1 open source package ship an affected version, including github.com/pgEdge/pgedge-rag-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/pgEdge/pgedge-rag-server` | Go | All versions | 1.0.1-0.20260729020411-a09d4872356b |

## How do I fix CVE-2026-125327?

Upgrade github.com/pgEdge/pgedge-rag-server to 1.0.1-0.20260729020411-a09d4872356b or later.

## Is CVE-2026-125327 being exploited?

There is no known exploitation of CVE-2026-125327 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125327 and fix it if it is affected.

What it is: CVE-2026-125327 is a high-severity vulnerability in pgedge-rag-server, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125327 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/pgEdge/pgedge-rag-server (Go): affected all versions; fixed in 1.0.1-0.20260729020411-a09d4872356b

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125327/ (Markdown: https://insights.sbomify.com/CVE-2026-125327/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125327
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125327
- OSV: https://osv.dev/vulnerability/CVE-2026-125327

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125327/
Summaries are generated and may contain mistakes; the official description above is the record.