Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 12 Nov 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | pgEdge Postgres MCP Server read-only mode can be bypassed by SQL statement smuggling through query_database | |
| Weaknesses | CWE-693 CWE-89 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-12T19:29:05.237Z
Reserved: 2026-11-10T20:07:44.957Z
Link: CVE-2026-126196
No data.
Status : Awaiting Analysis
Published: 2026-11-12T18:17:24.590
Modified: 2026-11-12T19:09:06.967
Link: CVE-2026-126196
No data.
OpenCVE Enrichment
No data.