CVE-2026-126199
pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients.
Impact
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.
An attacker can exploit this over the network, without logging in, but a user has to do something, such as open a file or a link. Specific conditions have to be met, which makes an attack harder. If it succeeds: high risk of data or systems being changed, high risk of outages.
Affected products · pgEdge
| Product | Affected versions |
|---|---|
| Pgedge-postgres-mcp | before 1.1.0 Version < 1.1.0 |
Weakness classification
References
- NVD record
- CVE.org record
- https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-5gmh-9683-hhq9
- https://github.com/pgEdge/pgedge-postgres-mcp/pull/233
- https://github.com/pgEdge/pgedge-postgres-mcp/commit/310c02809891cfaee6e4891cd7bb9aa1d459575c
- https://github.com/pgEdge/pgedge-postgres-mcp/releases/tag/v1.1.0