CVE-2026-125320
Received Received - Intake

pgEdge Postgres MCP Server Origin Header Validation Bypass

Publication date: 2026-11-10

Last updated on: 2026-11-10

Assigner: GitHub, Inc.

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-10
Last Modified
2026-11-10
Generated
2026-11-10
AI Q&A
2026-11-10
EPSS Evaluated
N/A
NVD
CVE-2026-125320
EUVD
EUVD-2026-121393

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
pgedge postgres_mcp_server 1.1.0
pgedge pgedge_postgres_mcp 1.1.0
pgedge pgedge_postgres_mcp to 1.1.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-346 The product does not properly verify that the source of data or communication is valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The vulnerability is in pgEdge Postgres MCP Server before version 1.1.0. It allows SQL queries against PostgreSQL databases via HTTP transport without validating the Origin header. This enables DNS rebinding attacks where an attacker can trick a user into visiting a malicious page that interacts with a locally running server to read database schemas and query results.

Detection Guidance

Check if pgEdge Postgres MCP Server is running version 1.1.0 or later. Inspect HTTP traffic for missing Origin header validation in the server logs. Verify if DNS rebinding attacks are possible by testing local server access from external domains.

Impact Analysis

If you use pgEdge Postgres MCP Server with HTTP transport enabled on a machine that also runs a browser, an attacker could exploit this to access your database schemas and query results. This could lead to unauthorized data exposure or manipulation of your database contents.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, potentially violating GDPR (data protection) and HIPAA (health information privacy) requirements. Organizations may face compliance violations, legal penalties, and reputational damage if exploited.

Mitigation Strategies

Upgrade pgEdge Postgres MCP Server to version 1.1.0 or later. Disable the HTTP transport if not required. Implement network-level protections against DNS rebinding attacks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-125320. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...