Quick answers
- Is CVE-2026-125325 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125325 being exploited in the wild.
- How severe is CVE-2026-125325?
- Medium severity, with a CVSS score of 5.9, published 10 November 2026.
- Which products and versions are affected?
- github.com/pgEdge/pgedge-rag-server (Go) < 1.0.1-0.20260729020411-a09d4872356b; pgEdge RAG Server before 2.0.0.
- Is there a fix for CVE-2026-125325?
- Yes: fixed in 2.0.0. Until then: Disable hybrid search using the disable_hybrid parameter on requests, or restrict network access to the unauthenticated query endpoint until upgrading to version 2.0.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125325 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-125325?
- Check whether you run github.com/pgEdge/pgedge-rag-server (Go) or pgEdge RAG Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.0.0
Disable hybrid search using the disable_hybrid parameter on requests, or restrict network access to the unauthenticated query endpoint until upgrading to version 2.0.0.
Technical details
The BM25 keyword index is a single per-pipeline object shared across unauthenticated requests with unsynchronized clear, refill, and search operations. Concurrent requests can interleave these operations, allowing a search to execute against a corpus populated by a different request's filter parameter, bypassing tenant isolation. The vulnerability requires no authentication or malformed input and is triggered by ordinary concurrent traffic to the unauthenticated query endpoint.
Affected products
- pgEdge RAG Server before 2.0.0
Identifiers
- CVE-2026-125325
- GHSA-w437-9mwm-j6vq
Timeline
- 2026-11-10: disclosed