pgEdge Go LLM Library discloses provider API key fragments in error messages
Historical advisory recorded 13 Nov 2026 16:56:54 UTC. Read the latest advisory.
cve-program · CVE-2026-125328
PublishedpgEdge Go LLM Library provides a unified Go interface for multiple LLM providers with streaming, tool calling, retries, and an HTTP and server-sent events proxy. From 0.1.0 until 0.2.0, GET /v1/health in llm/proxy/handlers.go uses handleHealth to ping providers with the operator's real credentials and returns their error text, while the Authorize hook in llm/proxy/proxy.go permits access by default when the consuming application does not configure it. When a provider rejects the configured credential, a remote caller who can reach the proxy can obtain part of the operator's third-party provider API key from the resulting error. This issue is fixed in version 0.2.0.
Read the publisher's advisoryAffected 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-125328 · CVE overview and exploitation status
cve-program · CVE-2026-125328
- https://github.com/pgEdge/pgedge-go-llm-lib/security/advisories/GHSA-8835-xmqj-354h
- https://github.com/pgEdge/pgedge-go-llm-lib/pull/26
- https://github.com/pgEdge/pgedge-go-llm-lib/commit/7531a55d368b3a29cd173c792cc4609c4134b076
- https://github.com/pgEdge/pgedge-go-llm-lib/commit/8bb9a6380d5f8db0124b51605759897034ad4da1
- https://github.com/pgEdge/pgedge-go-llm-lib/releases/tag/v0.2.0
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.