CVE-2026-126198: pgEdge Postgres MCP Server custom tools performed writes without user confirmation

Published Nov 12, 2026
·
Updated

pgEdge 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 querydatabase tool name instead of server-published write annotations. Custom pl-do, pl-func, and writing sql tools therefore ran without confirmation on allowwrites 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.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pgEdge Postgres MCP Server to a version that resolves this vulnerability.

    Fixed in 1.1.0

Event History

Nov 12, 2026
CVE Published
via MITRE·05:31 PM
Data Sourced
via MITRE·05:31 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to unconfirmed database writes?

Deployments using pgEdge Postgres MCP Server before 1.1.0 with its bundled CLI or web client are affected when they use an allow_writes connection and expose custom pl-do, pl-func, or writing sql tools. Other MCP clients do not inherit the bundled clients' confirmation behavior.

2

What must happen for an attacker to cause a write?

A write-capable custom tool must be available through an allow_writes connection, and the bundled client must invoke it. The issue can be triggered when a model follows instructions contained in retrieved content, because the client did not request confirmation for those custom writing tools.

3

Does the missing confirmation mean the server bypasses database authorization?

No. The affected control is a warning and confirmation mechanism in bundled clients, not a server-side authorization boundary. Database access remains governed by the permissions available to the configured connection.

4

What is the remediation?

Upgrade pgEdge Postgres MCP Server to version 1.1.0, which fixes the bundled clients' handling of server-published write annotations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203