CVE
pgEdge Postgres MCP Server read-only mode can be bypassed by SQL statement smuggling through query_database
Affects pgedge-postgres-mcp 1.0.0 and earlier, including alpha and beta pre-releases, where read_only is relied on as a safety boundary and the connecting role holds write privileges. 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 at version 1.0.0 or earlier, including alpha and beta pre-releases Deployment relies on read_only as a safety boundary Connecting role holds write privileges on the database
- 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? →
- 16/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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
pgEdge Postgres MCP Server's query_database tool can be bypassed by a remote attacker with low-privilege login, who sends unrecognized SQL statements containing multiple semicolon-separated statements to get around its read-only mode and combine writes with session changes when the connecting role has write privileges. This can compromise data integrity and availability, but it does not expose data beyond what the connection could already read.
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, query_database on a read_only connection could send unrecognized statements through pgx Exec without bind parameters, selecting PostgreSQL's simple query protocol and allowing multiple semicolon-separated statements in one request. A caller could combine transaction or session state changes with database writes, and pooled session state could leave later calls writable, when the connecting role held write privileges. The flaw affected deployments relying on read_only as a safety boundary, could compromise integrity and availability, and did not add confidentiality impact beyond the reads already permitted by the connection. This issue is fixed in 1.1.0.
Who should check
Teams running pgEdge Postgres MCP Server 1.0.0 or earlier that rely on read_only mode and connect with a write-capable database role.
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.1/10CVSS 8.1
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Deployment at version 1.0.0 or earlier, including alpha and beta pre-releases Deployment relies on read_only as a safety boundary Connecting role holds write privileges on the databaseUpgrade 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-126196 (pgEdge Postgres MCP Server read-only mode can be bypassed by SQL statement smuggling through query_database), 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-126196 (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 at version 1.0.0 or earlier, including alpha and beta pre-releases (source: https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-j7mp-839j-jrm7)
- Deployment relies on read_only as a safety boundary (source: https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-j7mp-839j-jrm7)
- Connecting role holds write privileges on the database (source: https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-j7mp-839j-jrm7)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126196 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126196 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-j7mp-839j-jrm7
- 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-126196
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-126196"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
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-126196
Is CVE-2026-126196 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?
A flaw lets someone with tool-call access to a read-only connection write to the database anyway, including creating, altering and dropping objects.Source: github.com
Which versions are affected by CVE-2026-126196?
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, where the deployment relies on read_only as a safety boundary and the connecting role holds write privileges on the database. To check, look at the installed pgedge-postgres-mcp version and the privileges of the database role it connects with.Source: github.com
How do I fix CVE-2026-126196?
Upgrade pgedge-postgres-mcp to version 1.1.0 or later, which is the fixed version.Source: github.com