pgEdge Postgres MCP Server read-only mode can be bypassed by SQL statement smuggling through query_database
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| pgEdge | pgedge-postgres-mcp | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Pgedge | Pgedge-postgres-mcp |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pgedge
Pgedge pgedge-postgres-mcp |
|
| Vendors & Products |
Pgedge
Pgedge pgedge-postgres-mcp |
| 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
|