SQL injection in pgEdge Postgres MCP Server via custom pl-do tools
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- SQL injection
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-89.
Summary
Versions of pgEdge Postgres MCP Server before 1.1.0 are affected. Custom pl-do tools interpolate JSON arguments into a PostgreSQL DO block with fixed dollar-quote tags, so crafted arguments can end the block and inject SQL (CWE-89). A remote attacker with low privileges can run extra statements, bypass read_only and access or modify data available to the connecting role, if at least one pl-do tool is configured.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade pgedge-postgres-mcp to version 1.1.0, which fixes this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · CNA pgedge-postgres-mcp (pgEdge) Fixed in 1.1.0
Timeline
- 2026-11-12 Threatist record created from CVE-2026-126197
- 2026-11-13 CISA SSVC decision points changed
References
Other 4
More pgEdge vulnerabilities
- TI-2026-88777 Unbounded corpus read in pgEdge RAG Server allows resource exhaustion CVSS 3.1HIGH 7.5
- TI-2026-90431 Read-only bypass in pgEdge Postgres MCP Server allows database writes CVSS 3.1HIGH 8.1
- TI-2026-87969 Trust rules in pgEdge Control Plane allow passwordless Postgres login CVSS 3.1HIGH 7.8
- TI-2026-87900 Rate limiting bypass in pgEdge Postgres MCP Server via X-Forwarded-For header CVSS 3.1MEDIUM 6.5
- TI-2026-88778 pgEdge Go LLM Library exposes provider API key fragments in error messages CVSS 3.1MEDIUM 5.8
- TI-2026-87972 pgEdge RAG Server leaks part of provider API key in error messages CVSS 3.1MEDIUM 5.8
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences