<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 13 Nov 2026 19:11:27 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-125326</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-125326</link>
      <description>&lt;p&gt;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&amp;#39;s credential for the third-party provider account through the query API error response. This issue is fixed in version 2.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#39;s credential for the third-party provider account through the query API error response. This issue is fixed in version 2.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-125326</guid>
    </item>
    <item>
      <title>GHSA-68g8-gh8f-7rhg — pgEdge RAG Server discloses part of the configured provider credential through API error messages</title>
      <link>https://db.gcve.eu/vuln/ghsa-68g8-gh8f-7rhg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/pgEdge/pgedge-rag-server&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated remote caller could read part of the operator&amp;#39;s configured LLM provider API key.&lt;/p&gt;
&lt;p&gt;The query API relayed the text of a provider error straight to the caller. That text carried the upstream provider&amp;#39;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&amp;#39;s key. A caller who can reach the endpoint can cause such a failure and read the result.&lt;/p&gt;
&lt;p&gt;**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.&lt;/p&gt;
&lt;p&gt;The disclosed material authenticates to a **third-party provider account** rather than to pgEdge software, which is why the severity carries Scope: Changed.&lt;/p&gt;
&lt;p&gt;`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:&lt;/p&gt;
&lt;p&gt;```go
var errResp ErrorResponse
if err := json.Unmarshal(body, &amp;amp;errResp); err != nil {
    return fmt.Errorf(&amp;#34;API error (status %d): %s&amp;#34;, resp.StatusCode, string(body))
}
return fmt.Errorf(&amp;#34;API error (status %d): %s&amp;#34;, resp.StatusCode, errResp.Error.Message)
```&lt;/p&gt;
&lt;p&gt;The first branch interpolates the entire unparsed response body. The second returns the prov…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/pgEdge/pgedge-rag-server&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated remote caller could read part of the operator&amp;#39;s configured LLM provider API key.&lt;/p&gt;
&lt;p&gt;The query API relayed the text of a provider error straight to the caller. That text carried the upstream provider&amp;#39;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&amp;#39;s key. A caller who can reach the endpoint can cause such a failure and read the result.&lt;/p&gt;
&lt;p&gt;**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.&lt;/p&gt;
&lt;p&gt;The disclosed material authenticates to a **third-party provider account** rather than to pgEdge software, which is why the severity carries Scope: Changed.&lt;/p&gt;
&lt;p&gt;`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:&lt;/p&gt;
&lt;p&gt;```go
var errResp ErrorResponse
if err := json.Unmarshal(body, &amp;amp;errResp); err != nil {
    return fmt.Errorf(&amp;#34;API error (status %d): %s&amp;#34;, resp.StatusCode, string(body))
}
return fmt.Errorf(&amp;#34;API error (status %d): %s&amp;#34;, resp.StatusCode, errResp.Error.Message)
```&lt;/p&gt;
&lt;p&gt;The first branch interpolates the entire unparsed response body. The second returns the prov…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-68g8-gh8f-7rhg</guid>
    </item>
  </channel>
</rss>
