Quick answers
- Is CVE-2026-125322 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125322 being exploited in the wild.
- How severe is CVE-2026-125322?
- Medium severity, with a CVSS score of 6.5, published 10 November 2026.
- Which products and versions are affected?
- pgEdge Postgres MCP Server before 1.1.0.
- Is there a fix for CVE-2026-125322?
- Yes: fixed in 1.1.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125322 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-125322?
- Check whether you run pgEdge Postgres MCP 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: 1.1.0
Technical details
The count_rows tool's where parameter was concatenated directly into SQL queries without sanitization, allowing blind SQL injection through subqueries. An attacker could use boolean-blind or error-based techniques to infer data from tables not named in the tool call, bounded only by the connected role's existing SELECT privileges. Multi-statement injection was correctly blocked by the read-only query guard; the vulnerability was specifically in subquery-based inference attacks.
Affected products
- pgEdge Postgres MCP Server before 1.1.0
Timeline
- 2026-07-29: disclosed
- 2026-11-10: patched
- 2026-11-10: advisory