Evidence · DiggingBeagle record
pgEdge read-only MCP query mode could run writes and contaminate pooled session state (original advisory or patch)
A tool advertised as read-only trusted statement-prefix checks rather than a transaction and role boundary, allowing writes when PostgreSQL credentials retained write grants.
- Published
- Sep 3, 2026
- Source role
- primary disclosure
Evidence record
A tool advertised as read-only trusted statement-prefix checks rather than a transaction and role boundary, allowing writes when PostgreSQL credentials retained write grants.
Claim-level citations (4)
- supportspgEdge read-only MCP query mode could run writes and contaminate pooled session state: The pgEdge read-only remediation combines single-statement extended-query execution with resetting the PostgreSQL session before returning it to the pool; a connection that cannot be safely reset must be discarded. A PostgreSQL login without database write grants remains a separate least-privilege boundary even when application-level read-only checks fail.
GHSA-j7mp-839j-jrm7, patches, connection cleanup and least-privilege database-role workaround
- supportspgEdge read-only MCP query mode could run writes and contaminate pooled session state: The vendor reproduced table creation, alteration and deletion in disposable PostgreSQL and documented version 1.1.0 fixes including single-statement extended execution and connection-state reset.
Impact, confirmed local write operations and affected versions
- supportspgEdge read-only MCP query mode could run writes and contaminate pooled session state: Unsupported SQL transaction and session variants could reach a multipstatement simple-query execution path, and altered connection settings could persist when the same pooled connection served another request.
Root causes and 1.1.0 mitigation description
- supportspgEdge read-only MCP query mode could run writes and contaminate pooled session state: The maintainer reproduced table creation, alteration and deletion against a disposable database while relying on application read_only; RESET ALL or DISCARD ALL could also leave a pooled PostgreSQL session writable for later requests.
GHSA-j7mp-839j-jrm7, Description, reproduced DDL effects, pooled session state, Patches