# CVE-2026-125322: pgEdge Postgres MCP Server SQL injection in the count_rows where parameter


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-fhv3-x3jh-grj7

## What is CVE-2026-125322?

CVE-2026-125322 is a medium-severity vulnerability in pgedge-postgres-mcp, published on 10 Nov 2026. 

### Official description

pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, the where parameter of the count_rows tool accepted subqueries against tables other than the table named in the tool call. A caller could use predicates and the returned row count as an inference oracle to extract data from any other table that the connected database role could read. The database privilege boundary remained intact, and the flaw did not grant access to tables outside that role's existing SELECT privileges. This issue is fixed in version 1.1.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2026-125322?


## How do I fix CVE-2026-125322?

No fix has been published for CVE-2026-125322 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-125322 being exploited?

There is no known exploitation of CVE-2026-125322 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125322 and fix it if it is affected.

What it is: CVE-2026-125322 is a medium-severity vulnerability in pgedge-postgres-mcp, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125322 in the wild and no public exploit code.

Affected product: pgedge-postgres-mcp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125322/ (Markdown: https://insights.sbomify.com/CVE-2026-125322/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125322
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125322
- OSV: https://osv.dev/vulnerability/CVE-2026-125322

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125322/
Summaries are generated and may contain mistakes; the official description above is the record.