CVSS 3.1
8.8 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVE-2026-126197 pgEdge Postgres MCP Server SQL injection through custom pl-do tool parameters
High (8.8) in pgedge pgedge-postgres-mcp. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
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.
Severity
- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
- OWASP Top 10
- A05:2025 Injection
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-126197 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126197?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126197?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126197 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-126197)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126197"><img src="https://cve.bz/cve/badge/CVE-2026-126197.svg" alt="CVE-2026-126197"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| pgedge-postgres-mcp | < 1.1.0 |
Attack patterns (CAPEC)
- CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
- CAPEC-66 SQL Injection Likelihood: High · Severity: High
- CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
- CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
- CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
- CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.