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

Status: published. Published: 2026-11-10. Updated: 2026-11-14.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- pgEdge / pgedge-postgres-mcp: < 1.1.0 (affected). Source: CNA: GitHub_M

## Severity and prioritization

- CVSS 3.1: 6.5 (medium); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N; source: CNA: GitHub_M

- CVSS 3.1: 6.5 (medium); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N; source: NVD: security-advisories@github.com

- CISA KEV: No listing in collected sources

- EPSS: 0.33% as of 2026-11-13; percentile 26.73%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: CWE-89, CWE-209

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-fhv3-x3jh-grj7 (CNA: GitHub_M; x_refsource_CONFIRM)

- https://github.com/pgEdge/pgedge-postgres-mcp/issues/200 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/pgEdge/pgedge-postgres-mcp/pull/201 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/pgEdge/pgedge-postgres-mcp/commit/933f1b4cb136183eb307064c1cf1ad2bf015f314 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/pgEdge/pgedge-postgres-mcp/releases/tag/v1.1.0 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/pgEdge/pgedge-postgres-mcp/commit/933f1b4cb136183eb307064c1cf1ad2bf015f314 (security-advisories@github.com)

- https://github.com/pgEdge/pgedge-postgres-mcp/issues/200 (security-advisories@github.com)

- https://github.com/pgEdge/pgedge-postgres-mcp/pull/201 (security-advisories@github.com)

- https://github.com/pgEdge/pgedge-postgres-mcp/releases/tag/v1.1.0 (security-advisories@github.com)

- https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-fhv3-x3jh-grj7 (security-advisories@github.com)

## Provenance

- CNA: GitHub_M: https://www.cve.org/CVERecord?id=CVE-2026-125322; retrieved 2026-11-14; source updated 2026-11-14

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125322; retrieved 2026-11-13; source updated 2026-11-12

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-125322; retrieved 2026-11-14; source updated Not reported

Revision: 276a6e990dac8c345d35950decc93e725e56e4d63ce90c8b6f75234143101f81

Canonical: https://y2.dev/cve/CVE-2026-125322

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.