CVE
pgEdge Postgres MCP Server SQL injection through custom pl-do tool parameters
Affects pgEdge Postgres MCP Server 1.0.0 and earlier, including alpha and beta pre-releases, in deployments that define a custom tool of type pl-do. CVSS scores it 8.8 High. Fixed in 1.1.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.1.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Deployment defines at least one custom tool of type pl-do Version 1.0.0 or earlier, including alpha and beta pre-releases
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The pgEdge Postgres MCP Server, in versions before 1.1.0, lets an attacker who has low-privilege access send crafted tool arguments over the network and inject SQL into custom pl-do tools, which can bypass read-only mode and read or change data the connecting database role can reach. The flaw only affects deployments that define at least one pl-do custom tool.
Read the original 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.
Who should check
Teams running pgEdge Postgres MCP Server 1.0.0 or earlier with at least one custom pl-do tool defined, including alpha and beta builds.
Not fixed by: Upgrading alone is not enough; the advisory says more action is needed.
Read the source excerpt
“Who is affected: any deployment of pgEdge Postgres MCP Server at 1.0.0”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Deployment defines at least one custom tool of type pl-do Version 1.0.0 or earlier, including alpha and beta pre-releasesUpgrade to a fixed version: 1.1.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126197 (pgEdge Postgres MCP Server SQL injection through custom pl-do tool parameters), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126197 (entry last updated 2026-11-12):
Affected:
- pgEdge pgedge-postgres-mcp: fixed in 1.1.0
Fixed versions: 1.1.0.
Conditions (all must be true for the bug to be hit):
- Deployment defines at least one custom tool of type pl-do (source: https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-r5pp-jx86-r6r9)
- Version 1.0.0 or earlier, including alpha and beta pre-releases (source: https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-r5pp-jx86-r6r9)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126197 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126197 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-r5pp-jx86-r6r9
- https://github.com/pgEdge/pgedge-postgres-mcp/pull/196
- https://github.com/pgEdge/pgedge-postgres-mcp/commit/b5b929305de7a22cd6ed7de8ae1be2ac90ca0868
- https://github.com/pgEdge/pgedge-postgres-mcp/releases/tag/v1.1.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126197
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126197"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- pgEdge pgedge-postgres-mcp
fixed in 1.1.0
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126197
Is CVE-2026-126197 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Parameters passed to custom pl-do tools can inject SQL, which runs as the connecting database role. That can include transaction control that bypasses read-only mode, and reading or modifying anything that role can reach.Source: github.com
Which versions are affected by CVE-2026-126197?
pgedge-postgres-mcp: before 1.1.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions 1.0.0 and earlier, including alpha and beta pre-releases, are affected, but only in deployments that define at least one custom tool of type pl-do. To check, review the server's custom tool configuration for pl-do tools and confirm the installed version.Source: github.com
How do I fix CVE-2026-126197?
Upgrade pgedge-postgres-mcp to 1.1.0 or later, which is the fixed version.Source: github.com