Skip to main content
VulnerabilityPublished

CVE-2026-126196: pgedge-postgres-mcp · SQL Injection

Affects pgedge-postgres-mcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 1.1.0 soon.

Data as of 12 Nov 2026, 17:35 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.1
Patch
Available – fixed in 1.1.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

Upgrade pgedge-postgres-mcp to 1.1.0.

Affected software

ProductAffectedFixed in
pgEdgepgedge-postgres-mcpAffected
  • <1.1.0
Fixed in
  • 1.1.0

AI-suggested

Upgrade to pgEdge pgedge-postgres-mcp version 1.1.0 or later, where this vulnerability is fixed. No other mitigation is necessary as the fix addresses the root cause.

Description

CVE-2026-126196 is a SQL Injection vulnerability in pgEdge pgedge-postgres-mcp versions prior to 1.1.0. The flaw allows SQL queries on read-only connections to execute multiple semicolon-separated statements without proper parameter binding, potentially enabling transaction or session state changes combined with database writes. This undermines the intended read-only safety boundary, risking data integrity and availability. The issue is fixed in version 1.1.0.

References

Community reviews

Loading reviews…