CVE-2026-125320: pgEdge Postgres MCP Server did not validate the Origin header, allowing DNS rebinding
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pgEdge Postgres MCP Serverto a version that resolves this vulnerability.Fixed in 1.1.0
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Deployments using the HTTP transport on a machine that also runs a browser are affected prior to version 1.1.0. The default stdio transport is not reachable through this attack path.
What must an attacker do to exploit it?
The attacker must induce a user to visit an attacker-controlled web page. That page can use DNS rebinding to reach the locally running HTTP server and access schema information and query results from configured databases.
What can be done if upgrading immediately is not possible?
Disable the HTTP transport and use the default stdio transport, which is not exposed through this path. Upgrading to version 1.1.0 fixes the Origin-header validation issue.