# CVE-2026-126197: pgEdge Postgres MCP Server SQL injection through custom pl-do tool parameters

> Attackers can inject SQL through custom pl-do tool arguments in pgEdge Postgres MCP Server, bypassing read-only mode.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-r5pp-jx86-r6r9

## What is CVE-2026-126197?

CVE-2026-126197 is a high-severity SQL injection vulnerability in pgedge-postgres-mcp, published on 12 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, custom pl-do tools interpolated JSON arguments into a PostgreSQL DO block delimited by fixed dollar-quote tags. An argument containing $mcp_custom_tool$ could terminate the block and inject arbitrary SQL statements, while $mcp_args$ could inject procedural code into a plpgsql block. Because the statement used the simple query protocol, injected text could include additional statements and transaction control, bypassing read_only and accessing data or modifying resources available to the connecting role. The issue requires at least one pl-do custom tool; sql and pl-func tools pass arguments as bind parameters and are not affected by this injection mechanism. This issue is fixed in 1.1.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-126197?

Only installations with a non-default setting turned on are exposed.


## How do I fix CVE-2026-126197?

No fix has been published for CVE-2026-126197 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126197 being exploited?

There is no known exploitation of CVE-2026-126197 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126197 and fix it if it is affected.

What it is: CVE-2026-126197 is a high-severity SQL injection vulnerability in pgedge-postgres-mcp, published on 12 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126197 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

Affected product: pgedge-postgres-mcp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126197/ (Markdown: https://insights.sbomify.com/CVE-2026-126197/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126197
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126197
- OSV: https://osv.dev/vulnerability/CVE-2026-126197

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126197/
Summaries are generated and may contain mistakes; the official description above is the record.