Quick answers
- Is CVE-2026-125320 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125320 being exploited in the wild.
- How severe is CVE-2026-125320?
- Medium severity, with a CVSS score of 5.3, published 10 November 2026.
- Which products and versions are affected?
- pgEdge Postgres MCP Server prior to 1.1.0.
- Is there a fix for CVE-2026-125320?
- Yes: fixed in 1.1.0. Until then: Disable the HTTP transport if not required; use only the default stdio transport. Alternatively, bind the HTTP server only to localhost (127.0.0.1) rather than all network interfaces (0.0.0.0) to limit exposure to local network attackers. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125320 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-125320?
- Check whether you run pgEdge Postgres MCP Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.1.0
Disable the HTTP transport if not required; use only the default stdio transport. Alternatively, bind the HTTP server only to localhost (127.0.0.1) rather than all network interfaces (0.0.0.0) to limit exposure to local network attackers.
Technical details
The HTTP transport failed to validate the Origin header on incoming requests, allowing DNS rebinding attacks. An attacker-controlled page could resolve its domain to 127.0.0.1, bypass same-origin policy checks, and issue MCP requests to the local server. The vulnerability affects deployments with HTTP transport enabled on machines running a browser; the default stdio transport is not exploitable via this path.
Affected products
- pgEdge Postgres MCP Server prior to 1.1.0
Timeline
- 2026-11-10: disclosed
- 2026-08-07: patched