pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients.
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.
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- PgEdge
- Product
- pgedge-postgres-mcp
- CVSS v3.1
- 5.3 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
- Fix
- available
- Weakness
- CWE-346
- Exposure class
- Database, AI infrastructure
- NVD status
- Received
Why it ranks 28 (Notable)
- CVSS v3.1 5.3 medium
- Product class: database, AI infrastructure
- Fix available
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.
Links
- NIST National Vulnerability Database (CVE API 2.0) (nvd.nist.gov)
- CVE-2026-125320 on this site · NVD · CVE.org · Vulnpedia
Related coverage
Other items that share a CVE or were clustered with this one.