Home › Vulnerabilities

pgAdmin 4 Flaw CVE-2026-116241: Update Now

Published November 1, 2026 · Last updated November 1, 2026

CVE Critical Patch

The short version: CVE-2026-116241 is a critical-severity security flaw in pgAdmin 4. The National Vulnerability Database (NVD) published it on October 30, 2026, and the score it lists is 9.9 out of 10. When FraudMeNot checked on November 1, 2026, CISA had not added CVE-2026-116241 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-116241

The record was filed by f86ef6dc-4d3a-42ad-8f28-e6d5547a5007. In its own words: "pgAdmin 4's Import/Export Data tool wraps a user's query export in a psql \copy (...) TO command and checks that the query's parentheses are balanced so that nothing can escape the wrapper. The check rejected a backslash inside a single-quoted string, but not inside a double-quoted identifier, where it treated the next double quote as closing the identifier. psql's \copy parser applies the connection's escape character to whichever quote opened a token, so with standard_conforming_strings off a backslash-escaped double quote does not close the identifier. pgAdmin's and psql's view of the quoting then diverged, a closing parenthesis hidden from the check ended the \copy (...) wrapper, and a following TO PROGRAM clause was executed by psql on the pgAdmin host, as the operating-system account running pgAdmin, before the server rejected the statement. An ordinary database role can turn standard_conforming_strings off for itself, and the Import/Export Data permission is granted to non-administrators by default. This is a bypass of the fix for CVE-2026-17566. The fix rejects any backslash inside a double-quoted identifier, as was already done for single-quoted strings, since its meaning depends on a server setting that cannot be known reliably when the query is validated. This issue affects pgAdmin 4: before 9.19."

Why pgAdmin 4 admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 rated CVE-2026-116241 9.9 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker needs a low-privilege account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping pgAdmin 4 running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.

Scores can differ between the vendor and NVD because each judges the worst realistic case differently. For this flaw, f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 gives it 9.4 (Critical, CVSS 4.0).

Affected pgAdmin 4 releases

According to the record, these releases are vulnerable:

  • versions before 9.19

The type of bug behind CVE-2026-116241

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-78, Improper Neutralization of Special Elements used in an OS Command. MITRE describes this class of bug as follows: "The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command before it is sent to a downstream component. (Roles: Attack-Focused, Common-Name, Attack-Focused)"
  • CWE-115, Misinterpretation of Input. MITRE describes this class of bug as follows: "The product misinterprets an input, whether from an attacker or another product, in a security-relevant fashion."

Vendor remediation for CVE-2026-116241

The vendor advisory remediation for operators of pgAdmin 4, quoted for this page, is: "Update pgAdmin 4 to version 9.19 or later, which the pgAdmin project's advisory (GHSA-3jx6-4898-6q3m, https://github.com/advisories/GHSA-3jx6-4898-6q3m) lists as the fixed release. Version 9.19 also fixes a separate login-lockout bypass in server mode (CVE-2026-116238). Until you can update, remove the Import/Export Data permission from roles that do not need it, since pgAdmin grants it to non-administrators by default, and keep pgAdmin server mode off the public internet. Database and IT administrators who run pgAdmin 4 in server mode for shared teams should act first."

What to do about it

  • Update now: Update pgAdmin 4 to version 9.19 or later, which the pgAdmin project's advisory (GHSA-3jx6-4898-6q3m, https://github.com/advisories/GHSA-3jx6-4898-6q3m) lists as the fixed release. Version 9.19 also fixes a separate login-lockout bypass in server mode (CVE-2026-116238). Until you can update, remove the Import/Export Data permission from roles that do not need it, since pgAdmin grants it to non-administrators by default, and keep pgAdmin server mode off the public internet. Database and IT administrators who run pgAdmin 4 in server mode for shared teams should act first.
  • Who should act: IT teams, managed service providers, and developers who run or ship pgAdmin 4. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from pgAdmin (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from October 30, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-116241. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-116241 record details from CISA and NVD

  • Attack complexity for CVE-2026-116241: low
  • CVE-2026-116241 CVSS scope: changed
  • NVD sub-scores for CVE-2026-116241: exploitability 3.1, impact 6.0.
  • Who mapped the weakness type: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 (Secondary)
  • References in the NVD record: 2.

Dates to know

  • October 30, 2026: NVD publishes CVE-2026-116241.
  • November 1, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-116241 is not listed.
  • October 30, 2026: most recent NVD update (record status: Received).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.