Read the docs

DNS rebinding in pgEdge Postgres MCP Server exposes database data

Priority LOW 23CWE-346Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-346.

Summary

pgEdge Postgres MCP Server before 1.1.0 does not validate the Origin header on incoming requests of its HTTP transport (CWE-346). An attacker-controlled web page can use DNS rebinding to reach a locally running server when a user visits it. The page can then read schemas and query results from the databases configured on that server. Only deployments with the HTTP transport enabled on a machine that also runs a browser are affected.

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 HTTP transport did not validate the Origin header on incoming requests. A user who visited an attacker-controlled page could be targeted through DNS rebinding, allowing the page to reach a locally running server and read schemas and query results from configured databases. The issue affected deployments with the HTTP transport enabled on a machine that also ran a browser, while the default stdio transport was not reachable through this path. This issue is fixed in version 1.1.0.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00145 3rd percentileScored 2026-11-16
Fix Fixed pgedge-postgres-mcp (pgEdge): 1.1.0

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

VendorProductAffected versionsFixed inStatusSource
pgEdgepgedge-postgres-mcpbefore 1.1.01.1.0Patch availableCNA
  • pgedge-postgres-mcp VendorpgEdge Affected before 1.1.0 Fixed in 1.1.0 Patch available CNA

Remediation

Upgrade pgEdge Postgres MCP Server to version 1.1.0, which fixes the 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

  1. 2026-11-10 Threatist record created from CVE-2026-125320
  2. 2026-11-13 CISA SSVC decision points changed

References

  • 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
See all 11 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences