pgEdge Postgres MCP Server write confirmation skipped for writes that begin with a reading keyword
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, the bundled CLI and web clients classified query_database statements only by their first keyword before deciding whether to display a write confirmation. SELECT INTO, data-modifying common table expressions beginning with WITH, and EXPLAIN ANALYZE of a write were treated as reads and could execute without confirmation on an allow_writes connection. Read-only connections remain protected by PostgreSQL transaction access mode, and EXPLAIN without ANALYZE and SELECT FOR UPDATE remain classified as reads. This issue is fixed in 1.1.0. | |
| Title | pgEdge Postgres MCP Server write confirmation skipped for writes that begin with a reading keyword | |
| Weaknesses | CWE-357 | |
| References |
|
|
| Metrics |
cvssV3_1
|