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 Go LLM Library discloses provider API key fragments in error messages

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2026-125328

Published

pgEdge 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.

Source published
10 Nov 2026 18:05:20 UTC
Source modified
13 Nov 2026 15:34:20 UTC
Saved here
13 Nov 2026 16:56:54 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

euvd · EUVD-2026-121710

Published

pgEdge 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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Nov 10, 2026, 6:05:20 PM

dateUpdated: Nov 13, 2026, 3:34:20 PM

Source published
Nov 10, 2026, 6:05:20 PM (timezone not stated)
Source modified
Nov 13, 2026, 3:34:20 PM (timezone not stated)
Saved here
16 Nov 2026 20:48:05 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

nvd · CVE-2026-125328

Published

pgEdge 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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-209 · CWE-522

Original publisher date fields

published: 2026-11-10T19:21:10.130

lastModified: 2026-11-13T16:17:46.517

Source published
10 Nov 2026 19:21:10 UTC
Source modified
13 Nov 2026 16:17:46 UTC
Saved here
14 Nov 2026 20:21:38 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

osv · GHSA-8835-xmqj-354h

Published

### Impact An unauthenticated caller could read part of the operator's configured LLM provider API key. The library's own health handler pings every configured provider using the operator's real credential and returns the resulting error text verbatim. Providers characteristically quote a partially masked form of the credential they rejected, so a failing ping published a fragment of the key. **The endpoint is unauthenticated by default.** `authorize()` returns true immediately when the consuming application sets no `Authorize` hook, so `GET /v1/health` is reachable by anyone who can reach the listening port unless the consumer opted in to authentication. **Who is affected:** any application embedding pgedge-go-llm-lib at `0.1.0` or `0.1.1` that exposes the bundled HTTP proxy without setting an `Authorize` hook. Both affected versions are released tags and resolve through the public Go module proxy. The disclosed material authenticates to a **third-party provider account** rather than to pgEdge software, which is why the severity carries Scope: Changed. Evidence at `v0.1.1`: `llm/proxy/handlers.go:296` (`handleHealth` returning `err.Error()` in `ProviderHealth.Error`), `llm/proxy/proxy.go:247` (`authorize()` defaulting to permit), and `llm/proxy/proxy.go:350` (`writeError` writing the error with no redaction). ### Patches **Fixed in `0.2.0`. Upgrade to `0.2.0` or later**, which redacts credentials from provider error messages unconditionally. The fix adds `llm/internal/redact`, with a follow-up anchoring word boundaries, and is pinned by tests in that package. **Note the version.** There is no `0.1.2` — it was never cut, and some earlier material named it in error. `0.2.0` is the first fixed release. **Upgrading does not undo a disclosure that already happened. Rotate any LLM provider credential configured on an affected version** where the proxy was reachable without an `Authorize` hook, particularly if a provider was rejecting that key at the time. ### Workarounds Set an `Authorize` hook on the proxy, which closes the unauthenticated route to the health endpoint. Restricting network access to the listening port limits who can reach it. Neither removes the underlying disclosure for a caller who does reach the endpoint.

Source published
12 Nov 2026 19:32:36 UTC
Source modified
12 Nov 2026 19:45:03 UTC
Saved here
12 Nov 2026 20:18:20 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Publisher rating · MODERATE

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 16 Nov 22:31 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current