# CVE-2026-126198: pgEdge Postgres MCP Server custom tools performed writes without user confirmation

Status: published. Published: 2026-11-12. Updated: 2026-11-13.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- pgEdge / pgedge-postgres-mcp: < 1.1.0 (affected). Source: CNA: GitHub_M

## Severity and prioritization

- CVSS 3.1: 3.1 (low); CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N; source: CNA: GitHub_M

- CVSS 3.1: 3.1 (low); CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N; source: NVD: security-advisories@github.com

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: CWE-357

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-v44x-hxg7-5cgc (CNA: GitHub_M; x_refsource_CONFIRM)

- https://github.com/pgEdge/pgedge-postgres-mcp/pull/198 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/pgEdge/pgedge-postgres-mcp/commit/c86d5cbe6d65c6debd0d0e909ce320271caa4d90 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/pgEdge/pgedge-postgres-mcp/releases/tag/v1.1.0 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/pgEdge/pgedge-postgres-mcp/commit/c86d5cbe6d65c6debd0d0e909ce320271caa4d90 (security-advisories@github.com)

- https://github.com/pgEdge/pgedge-postgres-mcp/pull/198 (security-advisories@github.com)

- https://github.com/pgEdge/pgedge-postgres-mcp/releases/tag/v1.1.0 (security-advisories@github.com)

- https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-v44x-hxg7-5cgc (security-advisories@github.com)

## Provenance

- CNA: GitHub_M: https://www.cve.org/CVERecord?id=CVE-2026-126198; retrieved 2026-11-13; source updated 2026-11-13

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126198; retrieved 2026-11-13; source updated 2026-11-12

Revision: e117eb3ebca7976fa598f8fc6902a42ff86ce3debc2b6a23ffaf993d2ace71ad

Canonical: https://y2.dev/cve/CVE-2026-126198

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.