# CVE-2026-126199: pgEdge Postgres MCP Server write confirmation skipped for writes that begin with a reading keyword

> Clients with read-only connections can run write queries like SELECT INTO without confirmation in pgEdge Postgres MCP Server.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-5gmh-9683-hhq9

## What is CVE-2026-126199?

CVE-2026-126199 is a medium-severity security feature bypass vulnerability in pgedge-postgres-mcp, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-357 (Insufficient UI Warning of Dangerous Operations)

## Which versions are affected by CVE-2026-126199?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-126199?

No fix has been published for CVE-2026-126199 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126199 being exploited?

There is no known exploitation of CVE-2026-126199 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126199 and fix it if it is affected.

What it is: CVE-2026-126199 is a medium-severity security feature bypass vulnerability in pgedge-postgres-mcp, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-126199 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: pgedge-postgres-mcp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126199/ (Markdown: https://insights.sbomify.com/CVE-2026-126199/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126199
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126199
- OSV: https://osv.dev/vulnerability/CVE-2026-126199

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126199/
Summaries are generated and may contain mistakes; the official description above is the record.