VulnerabilityPublished 12 Nov 2026

CVE-2026-126198: pgedge-postgres-mcp · Insufficient UI Warning of Dangerous Operations

Affects pgedge-postgres-mcpSource CVE Database V5

Compare

Not known to be exploited · CVSS 3.1 Low : upgrade to 1.1.0 when convenient.

Data as of 12 Nov 2026, 17:49 UTC

CVSS 3.1 base score

3.1Low

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	3.1

Patch: Available – fixed in 1.1.0

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade pgedge-postgres-mcp to 1.1.0.

Affected software

Product	Affected	Fixed in
pgEdgepgedge-postgres-mcp	Affected <1.1.0	Fixed in 1.1.0

AI-suggested

Upgrade pgEdge Postgres MCP Server to version 1.1.0 or later, where this issue is fixed. The fix ensures that bundled clients properly check server-published write annotations before requesting user confirmation for write operations. No additional mitigation is required as this is a client-side UI warning issue and does not affect server authorization.

Description

CVE-2026-126198 is a vulnerability in pgEdge Postgres MCP Server prior to version 1.1.0 where bundled clients (CLI and web client) insufficiently warn users before executing potentially dangerous write operations. This occurs because the clients only check for the query_database tool name to decide on write confirmation, ignoring server-published write annotations. As a result, some custom tools could perform write operations without user confirmation. The issue is limited to bundled-client UI warnings and does not affect server authorization. The vulnerability is fixed in version 1.1.0.

Impact

The impact is limited to insufficient user interface warnings for potentially dangerous write operations in bundled clients of pgEdge Postgres MCP Server. This could lead to unintended write operations being executed without explicit user confirmation. There is no impact on server authorization controls, and no confidentiality or availability impact is indicated. The CVSS score is low (3.1), reflecting the limited scope and low severity of the issue.

Summary

The vulnerability CVE-2026-126198 affects pgEdge Postgres MCP Server's bundled clients before version 1.1.0. These clients determine whether to request user confirmation for write operations by checking only the query_database tool name, rather than relying on server-published write annotations. Consequently, custom procedural language tools and SQL writing tools could execute write operations without prompting the user for confirmation on allow_writes connections. This is a UI warning deficiency rather than a server-side authorization flaw. Other MCP clients are not affected by this issue. The problem is resolved in pgEdge version 1.1.0.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Nov 2026, 17:49 UTC

WeaknessesCWE-357

Technical details

References

Community reviews

Related threats