Read the docs

Custom write tools skip confirmation in pgEdge Postgres MCP Server

Priority LOW 15CWE-357Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

pgEdge Postgres MCP Server before 1.1.0 has bundled clients, including the CLI and web client, that decide whether to request write confirmation by checking only for the query_database tool name (CWE-357). Custom pl-do, pl-func and writing SQL tools therefore run without confirmation on allow_writes connections, including when a model follows instructions in retrieved content. The confirmation is a bundled-client warning rather than a server authorization boundary, and other MCP clients do not inherit it.

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, the bundled clients, including the CLI and web client, decided whether to request write confirmation by checking only for the query_database tool name instead of server-published write annotations. Custom pl-do, pl-func, and writing sql tools therefore ran without confirmation on allow_writes connections, including when a model followed instructions in retrieved content. The affected control is a bundled-client warning rather than a server authorization boundary, and other MCP clients do not inherit that prompt. This issue is fixed in 1.1.0.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00253 16th percentileScored 2026-11-16
Fix Fixed pgedge-postgres-mcp (pgEdge): 1.1.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
pgEdgepgedge-postgres-mcpbefore 1.1.01.1.0Patch availableCNA
  • pgedge-postgres-mcp VendorpgEdge Affected before 1.1.0 Fixed in 1.1.0 Patch available CNA

Remediation

Update 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

  1. 2026-11-12 Threatist record created from CVE-2026-126198
  2. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2026-90432 SQL injection in pgEdge Postgres MCP Server via custom pl-do tools CVSS 3.1HIGH 8.8
  • 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
See all 11 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences