pgEdge Postgres MCP Server skips write confirmation for some queries
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- High
- Impact type
- —
- Confidentiality · integrity · availability
- None · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
pgEdge Postgres MCP Server versions before 1.1.0 have a flaw in the bundled CLI and web clients, which decide whether to show a write confirmation by checking only the first keyword of a query_database statement (CWE-357). SELECT INTO, data-modifying WITH statements, and EXPLAIN ANALYZE of a write are treated as reads and can run without confirmation on an allow_writes connection. An attacker who can drive the query tool can make unconfirmed writes, affecting integrity and availability, with user interaction required. Read-only connections remain protected by PostgreSQL transaction access mode.
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 CLI and web clients classified query_database statements only by their first keyword before deciding whether to display a write confirmation. SELECT INTO, data-modifying common table expressions beginning with WITH, and EXPLAIN ANALYZE of a write were treated as reads and could execute without confirmation on an allow_writes connection. Read-only connections remain protected by PostgreSQL transaction access mode, and EXPLAIN without ANALYZE and SELECT FOR UPDATE remain classified as reads. 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
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
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
- 2026-11-12 Threatist record created from CVE-2026-126199
- 2026-11-16 CISA SSVC decision points changed
References
Other 4
More pgEdge vulnerabilities
- 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
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences