CVE-2026-126198 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
The bundled pgEdge MCP clients asked for write confirmation only for the query_database tool, so custom write tools ran without a prompt on allow_writes connections. An attacker who can steer the model with retrieved content can get unconfirmed database writes through those tools.
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 with allow_writes enabled and custom write tools such as pl-do, pl-func or other SQL-writing tools. The issue is a bundled-client warning rather than a server authorization boundary, and other MCP clients do not inherit that prompt, so the risk sits with how the bundled CLI or web client is used. Teams with allow_writes off or read-only use can skip it.
Not affected if allow-writes-off, no-custom-write-tools, read-only-use
Who cares ai-agents, mcp, pgedge, postgresql
allow_writes setting in the server configuration1.1.0 or laterpgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, the bundled clients, including the CLI and web client, decided whether to request write confirmation by checking only for the query_database tool name instead of server-published write annotations. Custom pl-do, pl-func, and writing sql tools therefore ran without confirmation on allow_writes connections, including when a model followed instructions in retrieved content. The affected control is a bundled-client warning rather than a server authorization boundary, and other MCP clients do not inherit that prompt. 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.