No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Mon, 16 Nov 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 13 Nov 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pgedge
Pgedge pgedge-postgres-mcp |
|
| Vendors & Products |
Pgedge
Pgedge pgedge-postgres-mcp |
Thu, 12 Nov 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | pgEdge Postgres MCP Server SQL injection through custom pl-do tool parameters | |
| Weaknesses | CWE-89 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-13T18:57:22.759Z
Reserved: 2026-11-10T20:07:44.957Z
Link: CVE-2026-126197
Updated: 2026-11-13T18:57:09.272Z
Status : Awaiting Analysis
Published: 2026-11-12T18:17:24.780
Modified: 2026-11-13T19:19:23.773
Link: CVE-2026-126197
No data.
OpenCVE Enrichment
Updated: 2026-11-13T15:30:03Z