Read the docs

Read-only bypass in pgEdge Postgres MCP Server allows database writes

Priority LOW 36CWE-693Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass, SQL injection
Confidentiality · integrity · availability
None · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-693 and CWE-89.

Summary

pgEdge Postgres MCP Server before 1.1.0 fails to enforce read-only mode in query_database. Unrecognized statements run over PostgreSQL's simple query protocol, which accepts multiple semicolon-separated statements, so a caller can combine state changes with writes (CWE-89). A remote user with low privileges can alter data and affect availability when the connecting role holds write privileges.

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, query_database on a read_only connection could send unrecognized statements through pgx Exec without bind parameters, selecting PostgreSQL's simple query protocol and allowing multiple semicolon-separated statements in one request. A caller could combine transaction or session state changes with database writes, and pooled session state could leave later calls writable, when the connecting role held write privileges. The flaw affected deployments relying on read_only as a safety boundary, could compromise integrity and availability, and did not add confidentiality impact beyond the reads already permitted by the connection. This issue is fixed in 1.1.0.

Why it matters now

EPSS 0.00433 38th percentileScored 2026-11-16
Fix Fixed pgedge-postgres-mcp (pgEdge): 1.1.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

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 flaw.

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-126196

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-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
See all 11 →

Sources

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