Is there a public exploit for CVE-2026-125326?

No public exploit for CVE-2026-125326 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-125326?

CVE-2026-125326 scores CVSS 5.8 (v3.1), rated medium. EPSS puts the chance of exploitation in the next 30 days at 0.41%.

What does CVE-2026-125326 affect?

CVE-2026-125326 affects pgEdge github.com/pgEdge/pgedge-rag-server.

5.8 Medium

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

CVE-2026-125326

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 when pipeline execution failed. parseError in v1.0.0:internal/llm/openai/client.go produced that error by two routes, and both disclose: go var errResp ErrorResponse if err := json.Unmarshal(body, &errResp); err != nil {…

Assessment

CVSS: 5.8 (v3.1)
Severity: Medium
EPSS: 0.41% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 12 November 2026
Last updated: 12 November 2026
Affected: pgEdge · pgedge-rag-server · github.com/pgEdge/pgedge-rag-server
Weakness: CWE-209, CWE-522
Assigner: GitHub_M

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 4 + 8? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-125326