AI Stack Alert Medium CVE-2026-125320 For CISO, AppSec, AI Eng, SOC / IR AI-assisted
CVE-2026-125320: pgEdge Postgres MCP Server HTTP transport missing Origin validation enables DNS rebinding
pgEdge Postgres MCP Server versions prior to 1.1.0 did not validate the Origin header on HTTP transport requests. An attacker-controlled web page could use DNS rebinding to reach a locally running server and read schemas and query results from configured databases. The default stdio transport was not reachable through this path, and the issue is fixed in version 1.1.0.
Why it matters
Organizations running the HTTP transport on developer or user machines that also run a browser could have database schemas and query results exposed to a malicious web page. The CVSS base score is 5.3.
Do this
- Upgrade pgEdge Postgres MCP Server to version 1.1.0 or later.
- Identify deployments that have the HTTP transport enabled and confirm whether they run on hosts with a browser in use.
- Where upgrade is delayed, switch affected servers to the stdio transport or disable the HTTP transport.
- Restrict database credentials used by the MCP server to least privilege and review which schemas they can read.
Exploit Clock
Exploitation unlikely (for now)
- EPSS 0.14%
Signals
- NoCISA KEV
- 5.3CVSS
- 0.14%EPSS
- NoPublic PoC
- 27/100Priority
- 80%Confidence
Evidence
“Prior to 1.1.0, the HTTP transport did not validate the Origin header on incoming requests.”
“allowing the page to reach a locally running server and read schemas and query results from configured databases”
“This issue is fixed in version 1.1.0.”
Sources
Affected / related
pgEdge Postgres MCP Server, DNS rebinding
Published 2026-11-10 18:17 UTC · updated 2026-11-12 16:46 UTC · AI-assisted summary, checked against quoted sources · How we score