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.
- 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
- None listed
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
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.
Upgrade to the fixed version, and do not rely on a single control for protection. More about Security feature bypass.
Is CVE-2026-126199 being exploited?
There is no known exploitation of CVE-2026-126199 in the wild and no public exploit code.
Sources
Also known as GHSA-5gmh-9683-hhq9.