AI Stack Alert Medium CVE-2026-126199 For AppSec, AI Eng, SOC / IR AI-assisted
pgEdge Postgres MCP Server before 1.1.0 skips write confirmation for some SQL statements
pgEdge Postgres MCP Server prior to 1.1.0 classified query_database statements by their first keyword only. SELECT INTO, data-modifying WITH statements, and EXPLAIN ANALYZE of a write ran without confirmation on allow_writes connections. The issue is fixed in 1.1.0 and carries a CVSS base score of 6.8.
Why it matters
Users of bundled CLI and web clients on allow_writes connections could have data changed without the intended confirmation step. Read-only connections remain protected by PostgreSQL transaction access mode.
Do this
- Upgrade pgEdge Postgres MCP Server to version 1.1.0 or later.
- Review which MCP connections have allow_writes enabled and disable it where writes are not needed.
- Audit PostgreSQL logs for unexpected INSERT, UPDATE, or DELETE activity from MCP client sessions, including SELECT INTO and WITH statements.
- Confirm read-only connections use PostgreSQL read-only transaction access mode.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 6.8CVSS
- NoPublic PoC
- 26/100Priority
- 70%Confidence
Evidence
“the bundled CLI and web clients classified query_database statements only by their first keyword before deciding whether to display a write confirmation”
“This issue is fixed in 1.1.0.”
Sources
Affected / related
pgEdge Postgres MCP Server, SQL statement classification bypass
Published 2026-11-12 18:17 UTC · updated 2026-11-12 20:35 UTC · AI-assisted summary, checked against quoted sources · How we score