Skip to content
Fencer Intel
medium 6.8

CVE-2026-126199 json

pgEdge Postgres MCP Server write confirmation skipped for writes that begin with a reading keyword

published 4d ago modified 2d ago also EUVD-2026-124570 , GHSA-5gmh-9683-hhq9

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository pgEdge/pgedge-postgres-mcp. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits
0
none known

Summary

pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, the bundled CLI and web clients classified query_database statements only by their first keyword before deciding whether to display a write confirmation. SELECT INTO, data-modifying common table expressions beginning with WITH, and EXPLAIN ANALYZE of a write were treated as reads and could execute without confirmation on an allow_writes connection. Read-only connections remain protected by PostgreSQL transaction access mode, and EXPLAIN without ANALYZE and SELECT FOR UPDATE remain classified as reads. This issue is fixed in 1.1.0.

Patch / fix

Is CVE-2026-126199 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-14).

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H

Affected products

  • pgEdge pgedge-postgres-mcp

Classification

Weakness
  • CWE-357 Insufficient UI Warning of Dangerous Operations

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of pgEdge/pgedge-postgres-mcp published their own advisory on GitHub. Reviewed sources take precedence over it.