Evidence · DiggingBeagle record
pgEdge Postgres MCP count_rows SQL injection GHSA-fhv3-x3jh-grj7
Primary or origin disclosure used to qualify the underlying mechanism, stated prerequisites and limits. CVE-2026-125322 GHSA-fhv3-x3jh-grj7: count_rows table restriction defeated by where expression containing Boolean subquery selecting another table; repeated row counts leak information if MCP DB role already has access. Fix rejects subqueries.
- Source role
- primary disclosure
Evidence record
Primary or origin disclosure used to qualify the underlying mechanism, stated prerequisites and limits. CVE-2026-125322 GHSA-fhv3-x3jh-grj7: count_rows table restriction defeated by where expression containing Boolean subquery selecting another table; repeated row counts leak information if MCP DB role already has access. Fix rejects subqueries.
Claim-level citations (3)
- supportspgEdge MCP row counting permitted subqueries outside the requested table: The pgEdge count_rows filter accepted a WHERE subquery that referred to another table, potentially exposing information through repeated result counts even when that table was absent from the MCP tool surface.
GHSA-fhv3-x3jh-grj7, PoC and Fix, count_rows WHERE expression
- supportspgEdge MCP row counting permitted subqueries outside the requested table: The upstream reproducer does not establish a production data leak or a bypass of native PostgreSQL SELECT restrictions.
Impact, count_rows Boolean subquery and 1.1.0 repair
- supportspgEdge MCP row counting permitted subqueries outside the requested table: The pgEdge Postgres MCP Server count_rows tool accepted a where expression containing a subquery against an unrelated table. Repeated counts could reveal facts about that table even when the MCP tool did not expose it by name.
Impact, count_rows Boolean subquery and 1.1.0 repair