Skip to content
MediumVulnerabilityLLM-specific

GHSA-68g8-gh8f-7rhg: pgEdge RAG Server discloses part of the configured provider credential through API error messages

Published
Record updated
View JSON
Affected
  • github.com/pgEdge/pgedge-rag-server < 1.0.1-0.20260729022402-72e0785a6d7c
Fixed in
1.0.1-0.20260729022402-72e0785a6d7c
  • released July 28, 2026, 106 days before disclosure
Known exploitation
Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.
EPSS
0.4%

Summary

Versions 1.0.0 and earlier of pgEdge RAG Server, including alpha and beta pre-releases, relay raw LLM provider error text to API clients through internal/server/handlers.go and parseError in internal/llm/openai/client.go. The endpoint has no authentication in those versions, so an unauthenticated caller who triggers a provider authentication failure can read a fragment of the operator's provider API key, such as the sk-proj- prefix and final four characters for OpenAI.

Mitigation

Fixed in 2.0.0. Upgrade to 2.0.0 or later. Upgrading does not undo prior disclosure, so rotate any LLM provider credential configured on an affected version while the endpoint was reachable by untrusted callers. Workarounds, which do not remove the defect: 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 also avoids the disclosure in practice.