Quick answers
- Is CVE-2026-126197 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126197 being exploited in the wild.
- How severe is CVE-2026-126197?
- High severity, with a CVSS score of 8.8, published 12 November 2026.
- Which products and versions are affected?
- pgEdge Postgres MCP Server before 1.1.0.
- Is there a fix for CVE-2026-126197?
- Yes: fixed in 1.1.0. Until then: Disable pl-do custom tools if they are not required for your use case, as only pl-do tools are vulnerable; sql and pl-func tools are not affected by this injection mechanism. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126197 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-126197?
- 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 pl-do custom tools if they are not required for your use case, as only pl-do tools are vulnerable; sql and pl-func tools are not affected by this injection mechanism.
Technical details
The vulnerability exists in custom pl-do tools that interpolate JSON arguments into PostgreSQL DO blocks using fixed dollar-quote delimiters. An attacker can inject $mcp_custom_tool$ or $mcp_args$ strings to terminate the block and inject arbitrary SQL statements. Because these statements use PostgreSQL's simple query protocol, they can include additional statements and transaction control commands, bypassing read_only restrictions. The vulnerability requires at least one pl-do custom tool to be configured; sql and pl-func tools use bind parameters and are not affected.
Affected products
- pgEdge Postgres MCP Server before 1.1.0
Timeline
- 2026-11-12: disclosed