AI Stack Alert Medium CVE-2026-125326 For AppSec, AI Eng, CISO AI-assisted
CVE-2026-125326: pgEdge RAG Server leaks partial LLM provider API key via query API errors
pgEdge RAG Server is an API server for retrieval-augmented generation over PostgreSQL content using pgvector. Prior to version 2.0.0, its unauthenticated query API returns raw error text from failed LLM provider calls. That text can quote a partially masked submitted API key, and a remote caller can trigger an authentication failure to obtain part of the operator's provider credential.
Why it matters
Any exposed pgEdge RAG Server instance before 2.0.0 can leak fragments of the operator's third-party LLM provider API key to unauthenticated remote callers. Partial key exposure can help an attacker narrow down or combine leaked material and misuse the provider account.
Do this
- Upgrade pgEdge RAG Server to version 2.0.0 or later.
- Until patched, restrict network access to the query API so only trusted clients can reach it.
- Rotate the LLM provider API key used by RAG Server if the instance was reachable by untrusted callers before patching.
- Review provider account usage logs for unexpected requests or authentication failures tied to the RAG Server key.
- Confirm error responses from the query API no longer contain provider-returned text after upgrading.
Exploit Clock
Exploitation unlikely (for now)
- EPSS 0.41%
Signals
- NoCISA KEV
- 5.8CVSS
- 0.41%EPSS
- NoPublic PoC
- 27/100Priority
- 80%Confidence
Evidence
“Prior to 2.0.0, the unauthenticated query API in internal/server/handlers.go returns err.Error() from failed LLM provider calls”
“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.”
Sources
Affected / related
pgEdge RAG Server, pgvector
Published 2026-11-10 18:17 UTC · updated 2026-11-12 16:46 UTC · AI-assisted summary, checked against quoted sources · How we score