GHSA-6hg5-9f3w-c886: pgEdge Postgres MCP Server did not validate the Origin header, allowing DNS rebinding

Q: Which deployments are exposed to this attack path?

Deployments using the HTTP transport on a machine where a browser is also running are affected. The default stdio transport is not reachable through this DNS-rebinding path.

Q: What must an attacker do to exploit the issue?

A user must visit an attacker-controlled web page. The attacker can then use DNS rebinding to make that page reach the locally running HTTP server and read schemas or query results from configured databases.

Q: What data could be exposed?

An attacker may be able to read database schemas and query results from databases configured for the server. The provided information does not indicate integrity or availability impact.

Q: How can the issue be remediated?

Upgrade pgEdge Postgres MCP Server to version 1.1.0, which fixes the missing Origin-header validation. If upgrading is not immediately possible, avoiding the HTTP transport removes the described exposure path; the default stdio transport is not reachable through it.

Published Nov 10, 2026

Updated

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

1 affected component

pgEdge Postgres MCP Server<1.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade pgEdge Postgres MCP Server to a version that resolves this vulnerability.
Fixed in 1.1.0

Event History

Nov 10, 2026

CVE Published

via OSV·05:23 PM

Data Sourced

via OSV·05:23 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Which deployments are exposed to this attack path?

Deployments using the HTTP transport on a machine where a browser is also running are affected. The default stdio transport is not reachable through this DNS-rebinding path.

What must an attacker do to exploit the issue?

A user must visit an attacker-controlled web page. The attacker can then use DNS rebinding to make that page reach the locally running HTTP server and read schemas or query results from configured databases.

What data could be exposed?

An attacker may be able to read database schemas and query results from databases configured for the server. The provided information does not indicate integrity or availability impact.

How can the issue be remediated?

Upgrade pgEdge Postgres MCP Server to version 1.1.0, which fixes the missing Origin-header validation. If upgrading is not immediately possible, avoiding the HTTP transport removes the described exposure path; the default stdio transport is not reachable through it.

GHSA-6hg5-9f3w-c886: pgEdge Postgres MCP Server did not validate the Origin header, allowing DNS rebinding

Affected Software

Remediation

Event History

Frequently Asked Questions

Which deployments are exposed to this attack path?

What must an attacker do to exploit the issue?

What data could be exposed?

How can the issue be remediated?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are exposed to this attack path?

What must an attacker do to exploit the issue?

What data could be exposed?

How can the issue be remediated?