pgEdge pgedge-postgres-mcp
pgEdge Postgres MCP Server SQL injection through custom pl-do tool parameters
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.1.0
Fixed in 1.1.0
Mitigation
Upgrade pgedge-postgres-mcp to 1.1.0 or later.
References
- Vendor advisory github.com/pgEdge/pgedge-postgres-mcp/security…
- Patch github.com/pgEdge/pgedge-postgres-mcp/pull/196
- Patch github.com/pgEdge/pgedge-postgres-mcp/commit/b…
1 more
- Release notes github.com/pgEdge/pgedge-postgres-mcp/releases…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.