PGEDGE RAG SERVER · CVE-2026-125326 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
pgEdge RAG Server is an API server for retrieval-augmented generation over PostgreSQL. Before 2.0.0, its unauthenticated query API returns raw error text from failed LLM provider calls, which can quote a partially masked operator API key to any remote caller.
first public Sep 3, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running pgEdge RAG Server before 2.0.0 with the query API reachable by remote callers. The leak happens when an LLM provider call fails, so the exposed key is the operator's third-party provider credential. Deployments where the query API is behind authentication or not reachable from outside are less exposed.
Not affected if auth-required, internal-only
Who cares llm-providers, pgedge-rag-server, pgvector, postgresql
2.0.0 are affected.internal/server/handlers.go.2.0.0.pgEdge RAG Server is an API server for retrieval-augmented generation over PostgreSQL content using pgvector. Prior to 2.0.0, the unauthenticated query API in internal/server/handlers.go returns err.Error() from failed LLM provider calls, preserving provider-controlled error text that can quote a partially masked submitted API key. A remote caller can cause an authentication failure and obtain part of the operator's credential for the third-party provider account through the query API error response. This issue is fixed in version 2.0.0.
This page as .md ·
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.