Is there a public exploit for CVE-2026-125328?

No public exploit for CVE-2026-125328 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-125328?

CVE-2026-125328 scores CVSS 5.8 (v3.1), rated medium. EPSS puts the chance of exploitation in the next 30 days at 0.00291%.

What does CVE-2026-125328 affect?

CVE-2026-125328 affects github.com/pgEdge/pgedge-go-llm-lib.

5.8 Medium

pgEdge Go LLM Library discloses provider API key fragments in error messages

CVE-2026-125328

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…

Assessment

CVSS: 5.8 (v3.1)
Severity: Medium
EPSS: 0.00291% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 12 November 2026
Last updated: 12 November 2026
Affected: github.com/pgEdge/pgedge-go-llm-lib
Weakness: CWE-209, CWE-522

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

At the source

GitHub Advisories

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 9 + 3? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-125328