pgEdge RAG Server before 2.0.0 and Go LLM Library 0.1.x: unauthenticated DoS, provider API key fragments in errors, results leaking between requests (CVE-2026-125325 to 125328)
pgEdge RAG Server (retrieval-augmented generation over PostgreSQL/pgvector) 1.0.0 and earlier exposes an unauthenticated query endpoint with three flaws fixed in 2.0.0: each request reads the whole corpus and rebuilds a BM25 index (DoS), failed LLM calls return provider error text that quotes part of the operator's API key, and a shared keyword index can return one caller's filtered documents to another. pgEdge Go LLM Library 0.1.0-0.1.1 has the same key-fragment leak through its unauthenticated /v1/health endpoint, fixed in 0.2.0.
What it is
CVE-2026-125327 / GHSA-5qg5-rgp6-j5m5 (high, 7.5): hybrid search is on by default, and FetchDocuments queried the source table with no LIMIT, rebuilding an in-memory BM25 index on every request. Cheap unauthenticated queries cost the server and database work proportional to the corpus size.
CVE-2026-125326 / GHSA-68g8-gh8f-7rhg (5.8): the query API returned err.Error() from failed provider calls. Providers quote a partially masked copy of a rejected key, so a caller who triggers an auth failure gets a fragment of the operator's LLM API key.
CVE-2026-125325 / GHSA-w437-9mwm-j6vq (5.9): one BM25 index per pipeline was shared by all requests and cleared, refilled and searched under separate locks, so under normal concurrent load a search could run on a corpus another request's filter had loaded, defeating tenant or customer filters.
CVE-2026-125328 / GHSA-8835-xmqj-354h (5.8): pgedge-go-llm-lib's HTTP proxy pings every provider with the real credentials on GET /v1/health and returns the error text; authorize() allows everything when the embedding app sets no Authorize hook. Fixed in 0.2.0, which redacts credentials from provider errors.
How to check
- Check the pgedge-rag-server version you run (release tag or go.mod); 1.0.0 and all earlier alpha/beta builds are affected.
- Run go list -m github.com/pgEdge/pgedge-go-llm-lib in apps that embed the library; 0.1.0 and 0.1.1 are affected if the bundled proxy is exposed without an Authorize hook.
- Check whether the RAG query endpoint or the library's proxy port is reachable by anyone untrusted.
How to fix
- Upgrade pgEdge RAG Server to 2.0.0 or later and pgedge-go-llm-lib to 0.2.0 or later.
- Rotate the LLM provider API keys these services used if the endpoints were reachable by untrusted callers, and put the query endpoint behind authentication and rate limiting.
go list -m github.com/pgEdge/pgedge-go-llm-lib github.com/pgEdge/pgedge-rag-server 2>/dev/null
go get github.com/pgEdge/[email protected] Sources
- GHSA-5qg5-rgp6-j5m5: unbounded corpus read (CVE-2026-125327) ↗
- GHSA-68g8-gh8f-7rhg: API key fragments in errors (CVE-2026-125326) ↗
- GHSA-w437-9mwm-j6vq: shared keyword index (CVE-2026-125325) ↗
- GHSA-8835-xmqj-354h: pgedge-go-llm-lib key fragments (CVE-2026-125328) ↗
- pgEdge RAG Server v2.0.0 ↗
- NVD: CVE-2026-125327 ↗