<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-13T19:58:20.019734+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-125326</id>
    <title>fkie_cve-2026-125326</title>
    <updated>2026-11-13T19:58:20.029723+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-125326"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-68g8-gh8f-7rhg</id>
    <title>GHSA-68g8-gh8f-7rhg — pgEdge RAG Server discloses part of the configured provider credential through API error messages</title>
    <updated>2026-11-13T19:58:20.029773+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/pgEdge/pgedge-rag-server</p>
<p>### Impact</p>
<p>An unauthenticated remote caller could read part of the operator's configured LLM provider API key.</p>
<p>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.</p>
<p>**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.</p>
<p>The disclosed material authenticates to a **third-party provider account** rather than to pgEdge software, which is why the severity carries Scope: Changed.</p>
<p>`v1.0.0:internal/server/handlers.go:121` relayed `err.Error()` to the client when pipeline execution failed. `parseError` in
`v1.0.0:internal/llm/openai/client.go` produced that error by two routes, and both disclose:</p>
<p>```go
var errResp ErrorResponse
if err := json.Unmarshal(body, &amp;errResp); err != nil {
    return fmt.Errorf("API error (status %d): %s", resp.StatusCode, string(body))
}
return fmt.Errorf("API error (status %d): %s", resp.StatusCode, errResp.Error.Message)
```</p>
<p>The first branch interpolates the entire unparsed response body. The second returns the prov…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-68g8-gh8f-7rhg"/>
  </entry>
</feed>
