Skip to content

← Actionable
Medium, CVSS 5.8amended

pgEdge RAG Server discloses part of the configured provider credential through API error messages

CVE-2026-125326GHSA-68g8-gh8f-7rhg

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/pgEdge/pgedge-rag-server 1.0.1-0.20260729022402-72e0785a6d7c), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
EPSS
  • CVE-2026-125326: 0.41% estimated exploitation activity in the next 30 days; percentile 35.90 (FIRST EPSS, 2026-11-14). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact An unauthenticated remote caller could read part of the operator's configured LLM provider API key. The query API relayed the text of a provider error straight to the caller. That text carried the upstream provider's own message, and providers characteristically quote a partially masked form of the credential they rejected when authentication fails — so a failing provider call published a fragment of the operator's key. A caller who can reach the endpoint can cause such a failure and read the result. Who is affected: any deployment of pgEdge RAG Server at `1.0.0` or earlier, including all alpha and beta pre-releases, whose query endpoint was reachable by an untrusted party. The endpoint carries no authentication in the affected versions. The disclosed material authenticates to a third-party provider account rather than to pgEdge software, which is why the severity carries Scope: Changed. `v1.0.0:internal/server/handlers.go:121` relayed `err.Error()` to the client…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-68g8-gh8f-7rhg

  2. Revision 1 · created ·

    Published from ghsa record GHSA-68g8-gh8f-7rhg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-125326

Advisory: pgEdge RAG Server discloses part of the configured provider credential through API error messages
IDs: CVE-2026-125326, GHSA-68g8-gh8f-7rhg
Record: https://patchnext.com/advisories/cve-2026-125326 (revision 2, source checked 13 Nov 2026, 06:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/pgEdge/pgedge-rag-server 1.0.1-0.20260729022402-72e0785a6d7c. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/pgEdge/pgedge-rag-server: affected < 1.0.1-0.20260729022402-72e0785a6d7c; fixed in 1.0.1-0.20260729022402-72e0785a6d7c

## Suggested inspection (read-only)
- Go github.com/pgEdge/pgedge-rag-server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/pgEdge/pgedge-rag-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-68g8-gh8f-7rhg (GitHub-reviewed advisory GHSA-68g8-gh8f-7rhg lists affected ranges: Go github.com/pgEdge/pgedge-rag-server >=0 <1.0.1-0.20260729022402-72e0785a6d7c)
- Verified: https://osv.dev/vulnerability/GHSA-68g8-gh8f-7rhg (OSV record GHSA-68g8-gh8f-7rhg lists affected ranges: Go github.com/pgEdge/pgedge-rag-server >=0 <1.0.1-0.20260729022402-72e0785a6d7c (fixed))

Commands are suggestions: review each one before running it.

Loading voting…