# CVE-2026-126197: pgEdge Postgres MCP Server SQL injection through custom pl-do tool parameters

Status: published. Published: 2026-11-12. Updated: 2026-11-13.

pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, custom pl-do tools interpolated JSON arguments into a PostgreSQL DO block delimited by fixed dollar-quote tags. An argument containing $mcp_custom_tool$ could terminate the block and inject arbitrary SQL statements, while $mcp_args$ could inject procedural code into a plpgsql block. Because the statement used the simple query protocol, injected text could include additional statements and transaction control, bypassing read_only and accessing data or modifying resources available to the connecting role. The issue requires at least one pl-do custom tool; sql and pl-func tools pass arguments as bind parameters and are not affected by this injection mechanism. This issue is fixed in 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: 8.8 (high); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; source: CNA: GitHub_M

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

- CISA KEV: No listing in collected sources

- EPSS: 0.37% as of 2026-11-13; percentile 31.24%

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

- Weaknesses: CWE-89

## 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-r5pp-jx86-r6r9 (CNA: GitHub_M; x_refsource_CONFIRM)

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

- https://github.com/pgEdge/pgedge-postgres-mcp/commit/b5b929305de7a22cd6ed7de8ae1be2ac90ca0868 (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/b5b929305de7a22cd6ed7de8ae1be2ac90ca0868 (security-advisories@github.com)

- https://github.com/pgEdge/pgedge-postgres-mcp/pull/196 (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-r5pp-jx86-r6r9 (security-advisories@github.com)

## Provenance

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

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

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

Revision: 3467d8cf04e9c30303473dcba111699168df04084f65524df0a9d75e060d992a

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

## 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.