CVSS 3.1
3.1 lowCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:NCVE-2026-126198 pgEdge Postgres MCP Server custom tools performed writes without user confirmation
Low (3.1) in pgedge pgedge-postgres-mcp. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, the bundled clients, including the CLI and web client, decided whether to request write confirmation by checking only for the query_database tool name instead of server-published write annotations. Custom pl-do, pl-func, and writing sql tools therefore ran without confirmation on allow_writes connections, including when a model followed instructions in retrieved content. The affected control is a bundled-client warning rather than a server authorization boundary, and other MCP clients do not inherit that prompt. This issue is fixed in 1.1.0.
Severity
- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 17th 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: partial, 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-357 Insufficient UI Warning of Dangerous Operations
- 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-126198 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126198?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126198?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-126198 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-126198)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126198"><img src="https://cve.bz/cve/badge/CVE-2026-126198.svg" alt="CVE-2026-126198"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| pgedge-postgres-mcp | < 1.1.0 |