PGEDGE POSTGRES MCP SERVER · CVE-2026-126196 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
The pgEdge Postgres MCP Server lets MCP clients run SQL against PostgreSQL. Before 1.1.0, statements sent to query_database on a read-only connection could chain multiple semicolon-separated statements, letting a caller change data or session state when the database role had write privileges.
first public Sep 3, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running the pgEdge Postgres MCP Server before 1.1.0 that treat the read-only connection setting as their safety boundary, and whose database role can write. Deployments where the role is read-only at the database level, or that do not expose the server to MCP clients, are not exposed to the write bypass.
Not affected if read-only-database-role, version-1.1.0-or-later
Who cares mcp, pgedge, postgresql
1.1.0 is affected.read_only as the write-protection boundary and whether the connecting database role has write privileges.1.1.0.pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, query_database on a read_only connection could send unrecognized statements through pgx Exec without bind parameters, selecting PostgreSQL's simple query protocol and allowing multiple semicolon-separated statements in one request. A caller could combine transaction or session state changes with database writes, and pooled session state could leave later calls writable, when the connecting role held write privileges. The flaw affected deployments relying on read_only as a safety boundary, could compromise integrity and availability, and did not add confidentiality impact beyond the reads already permitted by the connection. This issue is fixed in 1.1.0.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.