nday
CVE-2026-116249

pgAdmin 4: Connection file paths and parameter keys escape the user's storage directory

pgadmin.org / pgAdmin 4

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags weakness typepath traversal accessnetworkno user interaction
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

path traversal
CWE-22, stated by the CNA PostgreSQL and NVD, republishing f86ef6dc-4d3a-42ad-8f28-e6d5547a5007CWE-73, stated by the CNA PostgreSQL and NVD, republishing f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
network
AV:N in CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:L/SC:H/SI:H/SA:N (CVSS 4.0) from the CNA PostgreSQL
no user interaction
UI:N in CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:L/SC:H/SI:H/SA:N (CVSS 4.0) from the CNA PostgreSQL
stage
DIS
disclosed
cvss
7.2 HIGH v4.0

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
10-30T19:55Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

In server mode pgAdmin 4 resolves a server's password file, SSL certificate, key, CRL and SSH tunnel identity file relative to the user's storage directory, but get_complete_file_path() only stripped leading slashes before joining the two. A path such as "../<another user>/.pgpass", set through the server dialog, the REST API or a servers.json import, therefore named another user's file, and connecting used that user's saved passwords, client certificate or SSH key. The sslkeylogfile connection parameter was passed to libpq unchanged, so a path outside storage let libpq create or append a file as the account running pgAdmin.

make_conninfo() also quoted connection parameter values but not their names, so a crafted parameter name could smuggle additional keyword=value pairs past these checks.

The fix requires the resolved path, with symbolic links followed, to stay inside the user's storage directory or the named shared storage directory, confines sslkeylogfile the same way, and accepts only exact libpq keywords as connection parameter names. A refused path or keyword is reported instead of letting libpq fall back to a default.

This issue affects pgAdmin 4: before 9.19.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:H
High: the attacker must evade or get around security measures such as ASLR or DEP, or obtain target-specific secrets
Attack requirements AT:P
Present: success depends on specific deployment or execution conditions, such as a race condition, a non-default setting or a position on the network path
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:L/SC:H/SI:H/SA:N

CVSS 4.0 vector from the CVE record, scored by the CNA PostgreSQL.

Event log

+DISdisclosed

CVE record published by PostgreSQL. CVSS 7.2, high.

src cvelist · nday , bulk import · raw
{
  "id": 5456,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-116249",
  "occurred_at": "2026-10-30T19:55:18.121Z",
  "observed_at": "2026-11-12T14:10:31.286634Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:L/SC:H/SI:H/SA:N",
      "version": "4.0",
      "base_score": 7.2,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2026-11-06T16:19:30.753762Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-10-30T19:55:18.121Z",
    "assigner_short_name": "PostgreSQL"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.