---
id: "CVE-2026-126199"
page: "https://infrastack.ai/live/CVE-2026-126199"
kind: "vulnerability"
aliases: ["CVE-2026-126199"]
title: "pgEdge Postgres MCP Server: writes ran without confirmation on allow_writes connections"
severity: "medium"
cvss: 6.8
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-agents", "ai-tooling", "mcp", "pgedge", "postgres"]
not_affected_if: ["read-only-connections", "version-1.1.0-or-later"]
published_at: "2026-11-12T18:17:25+00:00"
first_seen_at: "2026-11-12T18:40:39+00:00"
updated_at: "2026-11-12T18:42:53+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-126199", "first_seen_at": "2026-11-12T18:40:39+00:00"}]
exploit_sources: []
---

# pgEdge Postgres MCP Server: writes ran without confirmation on allow_writes connections

Link for people: https://infrastack.ai/live/CVE-2026-126199 (this .md is for agents)

The pgEdge Postgres MCP Server, which lets AI clients run SQL against PostgreSQL, classified some write statements as reads, such as SELECT INTO, data-modifying WITH queries and EXPLAIN ANALYZE of a write. On connections with allow_writes enabled, those statements ran without the write confirmation prompt.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed pgEdge Postgres MCP Server version; versions before `1.1.0` are affected.
- Look for connections configured with `allow_writes` enabled in the server configuration.

## Fix

- Upgrade pgEdge Postgres MCP Server to `1.1.0` or later.

## Timeline

- 2026-11-12T18:40:39+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-126199

## Documents

- [advisory] Vendor advisory: github.com https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-5gmh-9683-hhq9
- [fix] Patch: github.com https://github.com/pgEdge/pgedge-postgres-mcp/commit/310c02809891cfaee6e4891cd7bb9aa1d459575c
- [fix] Release notes: github.com https://github.com/pgEdge/pgedge-postgres-mcp/releases/tag/v1.1.0

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_