CVSS 3.1
5.8 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:NCVE-2026-125326 pgedge pgedge-rag-server: Insufficiently Protected Credentials
Medium (5.8) in pgedge pgedge-rag-server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/pgEdge/pgedge-rag-server 1.0.1-0.20260729022402-72e0785a6d7c.
On this page
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.
Severity
- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWEs
- CWE-209 Generation of Error Message Containing Sensitive Information
CWE-522 Insufficiently Protected Credentials - Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-125326 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125326?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125326?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125326 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-125326)
HTML:
<a href="https://cve.bz/cve/CVE-2026-125326"><img src="https://cve.bz/cve/badge/CVE-2026-125326.svg" alt="CVE-2026-125326"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| pgedge-rag-server | < 2.0.0 |
Fix and patched versions
github.com/pgEdge/pgedge-rag-server(Go): fixed in 1.0.1-0.20260729022402-72e0785a6d7c
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-68g8-gh8f-7rhg | Go | github.com/pgEdge/pgedge-rag-server | <1.0.1-0.20260729022402-72e0785a6d7c | 1.0.1-0.20260729022402-72e0785a6d7c |
Attack patterns (CAPEC)
- CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
- CAPEC-54 Query System for Information Likelihood: High · Severity: Low
- CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low
- CAPEC-463 Padding Oracle Crypto Attack Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-522 (13).
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.