# CVE-2026-125328: pgEdge Go LLM Library discloses provider API key fragments in error messages


- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-8835-xmqj-354h

## What is CVE-2026-125328?

CVE-2026-125328 is a medium-severity vulnerability in pgedge-go-llm-lib, published on 10 Nov 2026. 

### Official description

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.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2026-125328?

1 open source package ship an affected version, including github.com/pgEdge/pgedge-go-llm-lib.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/pgEdge/pgedge-go-llm-lib` | Go | All versions | 0.1.2-0.20260729024727-7531a55d368b |

## How do I fix CVE-2026-125328?

Upgrade github.com/pgEdge/pgedge-go-llm-lib to 0.1.2-0.20260729024727-7531a55d368b or later.

## Is CVE-2026-125328 being exploited?

There is no known exploitation of CVE-2026-125328 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125328 and fix it if it is affected.

What it is: CVE-2026-125328 is a medium-severity vulnerability in pgedge-go-llm-lib, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125328 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/pgEdge/pgedge-go-llm-lib (Go): affected all versions; fixed in 0.1.2-0.20260729024727-7531a55d368b

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125328/ (Markdown: https://insights.sbomify.com/CVE-2026-125328/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125328
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125328
- OSV: https://osv.dev/vulnerability/CVE-2026-125328

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125328/
Summaries are generated and may contain mistakes; the official description above is the record.