# CVE-2026-125326: pgEdge RAG Server discloses part of the configured provider credential through API 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-68g8-gh8f-7rhg

## What is CVE-2026-125326?

CVE-2026-125326 is a medium-severity vulnerability in pgedge-rag-server, published on 10 Nov 2026. 

### Official description

pgEdge RAG Server is an API server for retrieval-augmented generation over PostgreSQL content using pgvector. Prior to 2.0.0, the unauthenticated query API in internal/server/handlers.go returns err.Error() from failed LLM provider calls, preserving provider-controlled error text that can quote a partially masked submitted API key. A remote caller can cause an authentication failure and obtain part of the operator's credential for the third-party provider account through the query API error response. This issue is fixed in version 2.0.0.

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

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

1 open source package ship an affected version, including github.com/pgEdge/pgedge-rag-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/pgEdge/pgedge-rag-server` | Go | All versions | 1.0.1-0.20260729022402-72e0785a6d7c |

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

Upgrade github.com/pgEdge/pgedge-rag-server to 1.0.1-0.20260729022402-72e0785a6d7c or later.

## Is CVE-2026-125326 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- github.com/pgEdge/pgedge-rag-server (Go): affected all versions; fixed in 1.0.1-0.20260729022402-72e0785a6d7c

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-125326/ (Markdown: https://insights.sbomify.com/CVE-2026-125326/index.md)
```

## Sources

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

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