CVE-2026-126197
pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients.
Impact
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.
An attacker can exploit this over the network, with a regular user account, without any action by a user. If it succeeds: high risk of data being read, high risk of data or systems being changed, high risk of outages.
Affected products · pgEdge
| Product | Affected versions |
|---|---|
| Pgedge-postgres-mcp | before 1.1.0 Version < 1.1.0 |
Weakness classification
References
- NVD record
- CVE.org record
- https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-r5pp-jx86-r6r9
- https://github.com/pgEdge/pgedge-postgres-mcp/pull/196
- https://github.com/pgEdge/pgedge-postgres-mcp/commit/b5b929305de7a22cd6ed7de8ae1be2ac90ca0868
- https://github.com/pgEdge/pgedge-postgres-mcp/releases/tag/v1.1.0