Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

pgedge-rag-server · Vulnerability

CVSS 3.1 5.8 MEDIUMEUVD CVSS 3.1 5.8 CVSS 3.1 · [email protected] · Secondary 5.8 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/pgEdge/pgedge-rag-server 1.0.1-0.20260729022402-72e0785a6d7cKEV status unknown

cve-program · CVE-2026-125326

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-121708

Published

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.

Read the publisher's advisory

nvd · CVE-2026-125326

Published

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.

Read the publisher's advisory

osv · GHSA-68g8-gh8f-7rhg

Published

### Impact An unauthenticated remote caller could read part of the operator's configured LLM provider API key. The query API relayed the text of a provider error straight to the caller. That text carried the upstream provider's own message, and providers characteristically quote a partially masked form of the credential they rejected when authentication fails — so a failing provider call published a fragment of the operator's key. A caller who can reach the endpoint can cause such a failure and read the result. **Who is affected:** any deployment of pgEdge RAG Server at `1.0.0` or earlier, including all alpha and beta pre-releases, whose query endpoint was reachable by an untrusted party. The endpoint carries no authentication in the affected versions. The disclosed material authenticates to a **third-party provider account** rather than to pgEdge software, which is why the severity carries Scope: Changed. `v1.0.0:internal/server/handlers.go:121` relayed `err.Error()` to the client when pipeline execution failed. `parseError` in `v1.0.0:internal/llm/openai/client.go` produced that error by two routes, and both disclose: ```go var errResp ErrorResponse if err := json.Unmarshal(body, &errResp); err != nil { return fmt.Errorf("API error (status %d): %s", resp.StatusCode, string(body)) } return fmt.Errorf("API error (status %d): %s", resp.StatusCode, errResp.Error.Message) ``` The first branch interpolates the entire unparsed response body. The second returns the provider's own message, which for OpenAI quotes the `sk-proj-` prefix and the final four characters of the submitted key. ### Patches **Fixed in `2.0.0`. Upgrade to `2.0.0` or later.** The fix adds `internal/safeerr` and stops provider error text reaching API clients. **Upgrading does not undo the disclosure, and this needs action beyond upgrading. Rotate any LLM provider credential that was configured on an affected version while the endpoint was reachable by an untrusted caller**, particularly if that provider was rejecting the key at the time. A fragment already disclosed stays disclosed. ### Workarounds Place the server behind a proxy that rewrites 5xx response bodies, or terminate provider errors before they reach the API surface. Keeping provider credentials valid, so that no authentication failure is produced, also avoids the disclosure in practice. None of these removes the underlying defect, and none is a substitute for upgrading.

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2026-125326 · CVE overview and exploitation status

EUVD-2026-121708

GHSA-68g8-gh8f-7rhg

cve-program · CVE-2026-125326

euvd · EUVD-2026-121708

nvd · CVE-2026-125326

osv · GHSA-68g8-gh8f-7rhg

Related changes

Linked by CVE identifier
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 17 Nov 11:15 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current