AI Stack Alert High CVE-2026-126196 For CISO, AppSec, AI Eng, SOC / IR AI-assisted
CVE-2026-126196: pgEdge Postgres MCP Server read_only bypass via simple query protocol before 1.1.0
pgEdge Postgres MCP Server enables SQL queries against PostgreSQL through MCP-compatible clients. Prior to 1.1.0, query_database on a read_only connection could send unrecognized statements without bind parameters, allowing multiple semicolon-separated statements in one request. This could let a caller make database writes when the connecting role had write privileges, and the issue is fixed in 1.1.0.
Why it matters
Organizations that rely on read_only mode as a safety boundary for MCP-driven database access may have writable sessions they believe are read-only. The flaw affects integrity and availability of the database.
Do this
- Upgrade pgEdge Postgres MCP Server to version 1.1.0 or later.
- Identify deployments that use read_only connections and confirm whether the connecting database role holds write privileges.
- Restrict the database role used by MCP connections to least privilege, granting only SELECT where writes are not needed.
- Review database logs for unexpected INSERT, UPDATE, DELETE, or DDL statements from MCP server connections prior to patching.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 8.1CVSS
- NoPublic PoC
- 36/100Priority
- 80%Confidence
Evidence
“Prior to 1.1.0, query_database on a read_only connection could send unrecognized statements through pgx Exec without bind parameters”
“allowing multiple semicolon-separated statements in one request”
“This issue is fixed in 1.1.0.”
Sources
Affected / related
pgEdge Postgres MCP Server, Simple query protocol multi-statement read_only 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