pgEdge discloses four security advisories in RAG and LLM stack

GitHub's Advisory Database disclosed four security advisories covering pgEdge's open-source Postgres RAG Server and Go LLM Library on November 12, 2026, detailing an unauthenticated denial-of-service flaw, two separate API-key leak issues, and a cross-tenant data leak caused by a shared search index. The first advisory, pgEdge RAG Server unauthenticated resource exhaustion, is tracked as CVE-2026-125327.

Four advisories, four distinct bugs

• CVE-2026-125327 (GHSA-5qg5-rgp6-j5m5): high severity, CVSS 7.5, unauthenticated requests to the RAG Server's keyword search could rebuild a full in-memory BM25 index on every query, causing denial of service; fixed in version 2.0.0
• CVE-2026-125326 (GHSA-68g8-gh8f-7rhg): moderate severity, CVSS 5.8, the query API relayed upstream LLM provider error text verbatim, leaking partially masked API key fragments to unauthenticated callers; fixed in version 2.0.0
• CVE-2026-125325 (GHSA-w437-9mwm-j6vq): moderate severity, CVSS 5.9, a shared BM25 index across concurrent unauthenticated requests could return one caller's search results to another, breaking multi-tenant isolation; fixed in version 2.0.0
• CVE-2026-125328 (GHSA-8835-xmqj-354h): moderate severity, CVSS 5.8, the Go LLM Library's unauthenticated /v1/health endpoint returned raw provider error text that leaked partial API key credentials, affecting versions 0.1.0 up to but excluding 0.2.0; fixed in version 0.2.0

What it means for people building RAG and LLM apps

pgEdge's stack is an open-source Postgres-based RAG and LLM proxy used to build retrieval-augmented AI applications, so these bugs sit directly in production pipelines. The two credential-leak issues mean partial API keys could be exposed through plain error-text responses with no authentication required, and the shared-index bug means a multi-tenant deployment could silently return one customer's search results to another customer.

Fixed versions and next steps

• RAG Server versions prior to 1.0.1 (pre-2.0.0) are affected by the three RAG Server issues; upgrading to version 2.0.0 resolves all three
• Go LLM Library versions 0.1.0 up to but excluding 0.2.0 are affected by the credential-disclosure issue; upgrading to version 0.2.0 resolves it

Sources

• pgEdge RAG Server unauthenticated resource exhaustion (GitHub Advisory Database, November 12, 2026, official)
• pgEdge RAG Server LLM provider credential disclosure (GitHub Advisory Database, November 12, 2026, official)
• pgEdge RAG Server cross-request data leak (GitHub Advisory Database, November 12, 2026, official)
• pgEdge Go LLM Library API key fragment disclosure (GitHub Advisory Database, November 12, 2026, official)

Written with AI assistance, strictly from the sources listed above. Before it went live, automated checks verified its dates, sources and every language edition.