CVE-2026-125320 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
The pgEdge Postgres MCP Server, which lets AI clients run SQL against PostgreSQL, did not check the Origin header on its HTTP transport before version 1.1.0. A malicious web page visited in a browser on the same machine could use DNS rebinding to read database schemas and query results.
first public Sep 3, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running the pgEdge Postgres MCP Server with the HTTP transport enabled on a workstation or host that also runs a browser. The default stdio transport was not reachable through this path, so setups using only stdio can skip it.
Not affected if stdio-transport, version-1.1.0-or-later
Who cares developer-workstation, mcp, pgedge, postgresql
1.1.0.1.1.0.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.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.