SQL injection in pgEdge Postgres MCP Server count_rows where parameter
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure, SQL injection
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-209 and CWE-89.
Summary
pgEdge Postgres MCP Server before 1.1.0 is affected by an SQL injection flaw in the where parameter of the count_rows tool. The parameter accepts subqueries against tables other than the one named in the tool call, which is CWE-89. A remote caller with low privileges can use predicates and the returned row count as an inference oracle to extract data from any other table that the connected database role can read.
Written with Claude Haiku 5.5 from the sources below · 2026-11-10
Description from the CNA
pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, the where parameter of the count_rows tool accepted subqueries against tables other than the table named in the tool call. A caller could use predicates and the returned row count as an inference oracle to extract data from any other table that the connected database role could read. The database privilege boundary remained intact, and the flaw did not grant access to tables outside that role's existing SELECT privileges. This issue is fixed in version 1.1.0.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade pgEdge Postgres MCP Server to version 1.1.0, which fixes this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-10
- Fix · CNA pgedge-postgres-mcp (pgEdge) Fixed in 1.1.0
Timeline
- 2026-11-10 Threatist record created from CVE-2026-125322
- 2026-11-12 Priority changed: MEDIUM → LOW
- 2026-11-14 CISA SSVC decision points changed
References
Other 5
- https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-fhv3-x3jh-grj7
- https://github.com/pgEdge/pgedge-postgres-mcp/issues/200
- https://github.com/pgEdge/pgedge-postgres-mcp/pull/201
- https://github.com/pgEdge/pgedge-postgres-mcp/commit/933f1b4cb136183eb307064c1cf1ad2bf015f314
- https://github.com/pgEdge/pgedge-postgres-mcp/releases/tag/v1.1.0
More pgEdge vulnerabilities
- TI-2026-90432 SQL injection in pgEdge Postgres MCP Server via custom pl-do tools CVSS 3.1HIGH 8.8
- TI-2026-88777 Unbounded corpus read in pgEdge RAG Server allows resource exhaustion CVSS 3.1HIGH 7.5
- TI-2026-90431 Read-only bypass in pgEdge Postgres MCP Server allows database writes CVSS 3.1HIGH 8.1
- TI-2026-87969 Trust rules in pgEdge Control Plane allow passwordless Postgres login CVSS 3.1HIGH 7.8
- TI-2026-87900 Rate limiting bypass in pgEdge Postgres MCP Server via X-Forwarded-For header CVSS 3.1MEDIUM 6.5
- TI-2026-88778 pgEdge Go LLM Library exposes provider API key fragments in error messages CVSS 3.1MEDIUM 5.8
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences