pgEdge Postgres MCP Server Statement Processing Vulnerability (CVE-2026-126196)
The pgEdge Postgres MCP Server allows users to execute multiple semicolon-separated SQL statements in a single request, potentially bypassing intended read-only restrictions.
CVE search metadata
CVE search record: CVE-2026-126196. Severity: high. CVSS: 8.1. KEV: no. Product: Postgres MCP Server (< 1.1.0). Brief: pgEdge Postgres MCP Server Statement Processing Vulnerability (CVE-2026-126196). Brief link: https://feed.craftedsignal.io/briefs/2026-11-pgedge-mcp-sql-injection-cve-2026-126196/
Triage facts
Revision 1- Applicability
- Postgres MCP Server (< 1.1.0)
- Evidence
- Unknown
- Severity
- High
- Sources
- 1 public source
- Freshness
- Revision 1Nov 12, 18:51 UTC
- Vulnerabilities
- 1 CVE
- Source quality
- A2Roughly even chance
The pgEdge Postgres MCP Server, in versions prior to 1.1.0, is susceptible to an issue where queries are processed using PostgreSQL's simple query protocol. This allows multiple semicolon-separated statements to be executed in one request. When an MCP client communicates with a database configured for read-only connections, a user may be able to execute unauthorized write operations or modify session states if the connecting database role possesses write privileges.
Impact
This vulnerability can compromise database integrity and availability by allowing unauthorized SQL statements to execute. Confidentiality is not impacted beyond what is already permitted by the database role.
Recommendation
Upgrade the pgEdge Postgres MCP Server to version 1.1.0 or later.